approve_delivery

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present, so description covers key behavior: irreversible on-chain action and return values. Does not specify authentication or permission details but is adequate for a simple approve action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear paragraphs and an Args section. Every sentence adds value; no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, behavior, and parameter meaning. Output schema exists and return values are mentioned. Complete for a simple tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (job_id) with 0% schema coverage. Description adds 'The contract ID to approve', which provides necessary context beyond the schema's title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Approve a delivered Mode B contract as the requester (Alice)', specifying verb, resource, and role. Distinguishes from siblings like dispute_delivery and submit_delivery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use instructions: after reviewing deliverable, before claiming payment. Warns that approval is irreversible and only after thorough testing. Lacks explicit mention of alternatives but context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.