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

Goes well beyond annotations, which only flag it as destructive and non-idempotent. It discloses that nothing is charged, the buyer is notified, a spending-limit reservation is released, the row persists as declined, and the pending slot reopens – all critical side effects an agent must know.

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?

Two sentences, front-loaded with the action and followed by exactly the consequences an agent needs. No filler.

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?

For a destructive single-param mutation with no output schema, the description covers the action, side effects, persistence, and slot semantics. Nothing essential is missing; return behavior is implicit in the success narrative.

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, request_id, and schema coverage is 100%, so baseline is 4. The description adds that the request must be pending and on your own offer, which qualifies the parameter beyond the schema's UUID format.

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?

States a specific verb (decline) and resource (pending request on your own offer), and clearly distinguishes from siblings like accept_request and withdraw_request. The scope 'on your own offer' rules out acting on someone else's request.

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?

Implies usage for a pending request the seller doesn't want to accept, and the note about freeing the pending slot signals the consequence. It doesn't explicitly name alternatives (e.g., use accept_request instead, or withdraw_request for buyers), but the context is clear enough to select it.

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