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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds value beyond that by clarifying the no-side-effect boundary (no reprice/renew/approve) and the tenancy scope ('within this account and OAuth client'). It stops short of saying what happens for an unknown, expired or cross-client quoteId.

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?

Three short sentences, each earning its place: what is returned, what is not done, and where to go instead. The key facts (read-only, returns amount/expiry/state) are front-loaded with no filler.

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 a single-parameter schema, no output schema and full annotation coverage, the description supplies the returned fields explicitly (amount, expiry, quote state) plus tenancy scoping and the sibling fallback. The only meaningful gap is failure behavior for a missing or stale quoteId, which a caller would likely want before invoking.

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 0%, so the description must carry parameter meaning, and it does add scope semantics the schema cannot express: the quoteId is resolved within this account and OAuth client, and the same quoteId is reusable against get_recast_status. It omits any note on invalid/expired quoteId behavior, which keeps it below a 5.

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 states a specific verb ('Read'), a specific resource ('Recast quote'), and the exact fields surfaced ('exact Recast amount, expiry and quote state'), keyed on quoteId. It also implicitly separates itself from get_recast_status by describing a read of the quote rather than job recovery, so an agent can route without opening either schema.

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?

It gives clear exclusions ('does not reprice, renew or approve') and names the alternative call for a different need: 'Use get_recast_status with the same quoteId to recover any submitted job.' It does not say when to prefer this over prepare_recast or compare_generation_prices, but the core when/when-not split for quote reading versus job status is explicit.

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