cancelAllQuotes

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

Describes return type (array of results with status per quote) and rate limit. No annotations provided, so description carries full burden. Adequately discloses behavior without contradictions.

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?

Very concise, two paragraphs with clear structure. Includes purpose, return type, rate limit, and agent hint. No unnecessary words.

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?

Full coverage for a simple tool: describes action, return format, and rate limit. No output schema, but return type is adequately explained. Meets all needs.

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?

No parameters, schema coverage 100%. Description adds value by stating 'no request body parameters needed', confirming the empty schema and clarifying usage.

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 it cancels all active quotes for the authenticated account. Distinguishes from sibling cancelQuote (singular) and cancelAllRfqs (different entity).

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?

Explicitly says it cancels all at once with no request body. Implies this is for bulk cancellation, while cancelQuote is for individual. Lacks explicit when-not-to-use but context with siblings provides clarity.

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