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

Goes well beyond the annotations by disclosing concrete side effects: it 'Stores a quote revision and makes a provider price check,' and it explicitly disclaims charging, reserving, holding, or inviting. This reconciles cleanly with readOnlyHint=false and destructiveHint=false, telling the agent exactly what write occurs.

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?

Front-loaded with purpose, then effects, then explicit non-effects — four tight sentences with little waste. The 'The quote states any provider-side effect of quoting' sentence is slightly meta but still informative.

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 tool with no output schema and a write side effect, the description adequately covers what it does, what it stores, and what it deliberately avoids. It could say more about the quote's expiration timing and return shape, but nothing critical is missing for correct invocation.

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 100% and every parameter carries a detailed description (ref prefixes, request_key retry semantics), so the schema does the heavy lifting. The description adds no parameter-level detail, making the baseline 3 appropriate.

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 and resource: 'Gets an expiring, exact price and terms for a selected offer.' Clearly distinct from the cancellation-quote sibling by scope. However, it never names a sibling or scope boundary explicitly, so an agent must infer the distinction from the resource alone.

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 'never charges, reserves, holds a seat or invites anyone' line implies this is a pre-booking pricing step, giving implied when-to-use context. But there is no explicit routing against alternatives like anywayr_prepare_checkout or anywayr_quote_cancellation, and no stated prerequisites.

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