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

The description makes the destructive nature clear through the word 'withdraw' and the condition 'before seller has quoted'. The annotations already mark it destructive and non-idempotent, and the description adds useful context without contradicting them.

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?

The description is a single concise sentence that conveys the action, timing, and actor restriction without unnecessary detail.

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?

With one well-described parameter and no output schema, the description provides all essential context needed to call the tool correctly. The conditions and effects are clearly stated.

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?

The only parameter, service_quote_id, is fully described in the schema as a UUID of the quote request to withdraw. The tool description does not add further parameter detail, but schema coverage is complete.

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 the action (withdraw a quote request), the specific resource (quote request), and the applicable conditions (before seller has quoted, buyer-only). This distinguishes it from related quote actions like reject or counter.

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 explicit timing (before seller has quoted) and actor restriction (buyer-only), giving clear guidance on when this tool is appropriate. It does not explicitly name alternative tools, but the conditions are sufficient.

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