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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'No side effects' merely restates that. The description adds nothing the structured fields don't cover — nothing about whether the returned price is persisted, how rounding/currency works, or that quote_id must reference an existing quote.

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 short sentences with zero filler; the scope statement is front-loaded and the safety note trails it. Nothing to trim.

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 pricing calculation with a nested options object and no output schema, an agent still doesn't know what comes back (a total only, or a line-item breakdown) or whether unmentioned add-ons inherit from the original quote. Adequate but with real gaps.

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 only 25%, but the description maps its three mutable dimensions (qty, color, options) onto the parameters, and the nested option fields carry rich per-option descriptions in the schema itself. quote_id's requirement (must be an existing quote) is only implied by 'existing quote'.

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?

States a specific verb (price) and resource (an existing quote) plus the dimensions being varied (quantity, color, add-ons). 'Existing' distinguishes it from quote_file, but that sibling is not named, so differentiation is inferred rather than stated.

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?

The phrase 'for another quantity, color or add-ons' implies the scenario (re-pricing an already-created quote), but there is no explicit when-to-use/when-not guidance and no reference to alternatives like create_checkout or quote_file.

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