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

Description details side effects (calculates pricing, writes record, returns URL) and clearly states what it does NOT do. Annotations show readOnlyHint=false, destructiveHint=false, consistent with writing a record. Provides context beyond annotations.

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, no wasted words. First sentence covers purpose and timing, second covers exclusions. Highly efficient and easy to parse.

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?

Given 3 parameters, present siblings, and existing output schema, the description covers purpose, usage timing, behavior, and limitations comprehensively. No gaps noted.

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?

All 3 parameters have schema descriptions (100% coverage). Description adds context about 'complete draft' and consent requirement but does not significantly enhance parameter meaning beyond the schema. Adequate baseline given schema coverage.

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?

Description clearly states verb 'generate' on resource 'quote' with specific context 'after user explicitly confirms a complete ShipMyCar quote draft'. Distinguishes from sibling tools (quote_get_requirements, quote_update_draft) by focusing on final generation step.

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 instructs when to use: after explicit user confirmation of a complete draft. Also states what it does not do (no email, no booking). Lacks explicit exclusions for other scenarios, but positive guidance is strong.

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