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

Goes well beyond the annotations by disclosing the concrete consequences of the destructive flag: open offers are withdrawn and bidding businesses are notified, and the action cannot be undone. This tells the agent what gets destroyed and who is affected, which is exactly the context annotations alone cannot convey.

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?

Three tight sentences: action, consequence, precondition. The irreversible consequence is front-loaded before the usage constraint, and no sentence is 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 mutation tool with no output schema but rich annotations, the description covers the essential ground: what it does, what it destroys, and when it may be called. It does not state the return or confirm what happens to the request record itself afterward, a minor residual gap.

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?

Schema description coverage is 100%, so request_id, access_key, and reason are already documented with patterns and provenance ('returned by create_request'). The description adds no parameter-level meaning, which matches the baseline for a fully documented schema.

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?

Names a specific verb and resource ('Cancel a Bidit request') and the irreversibility clause immediately scopes the operation. An agent can distinguish this from create_request, update_request, and submit_request without opening any schema.

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?

Gives an explicit gating condition: 'Only call this when the customer explicitly asks to cancel.' That is real when-to-use guidance with an implied when-not. It stops short of naming alternatives (e.g., update_request for modifications), so it is not a full 5.

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