AISEND / OIL
What belongs in a tool contract?
Architecture concept · In review. This describes the intended Aisend architecture. It is not evidence that the capability is deployed, integrated or available for purchase.
Short answer
A tool contract defines the task boundary, expected data, permissions and failure behaviour.
What it means
A contract makes a tool’s role inspectable before it is used. It describes what the operation accepts and returns, and the conditions under which it should not run.
How it fits
Include an operation name, input schema, output schema, permission scope, approval rule, timeout, retry policy and audit event. Distinguish read operations from writes. Use fictional adapter names in public examples unless an integration has been verified.
Scope and limitations
A well-written contract is not evidence that a tool is reliable or that its outputs are true. Implementation and testing remain necessary.