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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the response carries 'warnings' and 'next_steps', a useful behavioral hint about output content, but says nothing about freshness/expiry of the quote or error behavior for an unknown id.

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?

One compact sentence with no filler, and the most decision-relevant element (current pricing) is front-loaded. The trailing list of output categories is slightly enumerative but still earns its space.

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 an output schema present, the description needn't explain return values, and it correctly does not attempt to. Combined with annotations covering the read-only profile and a single well-documented required param, this is nearly sufficient; only usage routing to siblings is missing.

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 coverage is 100% and the single quote_id parameter is already documented as a 'qt_...' id from create_quote, so the description contributes nothing parameter-specific. Baseline 3 applies when the schema carries the full burden.

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?

The description names the resource (a quote) and enumerates the data it surfaces — pricing, speeds, shipping options, warnings, next_steps — which is more concrete than the bare name. However it never states the verb explicitly (retrieve/fetch a quote by id) and does nothing to distinguish it from siblings like get_order or get_quote-adjacent tools, so an agent must infer the retrieval semantics.

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?

There is no statement of when to call this versus create_quote, update_quote, or get_order, and no prerequisites. The only usage hint is indirect, coming from the schema's note that quote_id is 'returned by create_quote', which is not in the description itself.

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