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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description adds substantive context beyond that — it discloses the auth requirement, that the call never places a provider order or takes payment (bounding the side effect), and an availability precondition. It does not cover idempotency, whether the underlying quote is mutated, or what notification is emitted, so it stops short of 5.

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?

Four short sentences with the purpose front-loaded and no filler; the constraints follow in priority order. Minor wording awkwardness ('quoting access token' versus the quoteAccessToken property name) is the only blemish.

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?

No output schema exists, so the description needn't explain returns, and it does cover auth, side-effect scope, and availability. Still, for a 5-parameter mutation it omits what the notes field does and how quoteRequestId versus quoteId are used, leaving an incomplete picture 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?

With 5 parameters and 0% schema description coverage, the description carries the full burden, yet it only assigns meaning to two of them (access token, contact email). quoteRequestId, quoteId, and notes are entirely undocumented, and the distinction between quoteRequestId and quoteId is never explained.

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 concrete verb and resource: 'Request human review of a saved quote,' which an agent can distinguish from create_quote (creates), get_quote (reads), and list_providers (lists). It does not name a sibling to route against, so it falls short of the 5 bar, but the purpose itself is unambiguous.

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?

'Requires quoting access token and contact email' and 'Unavailable until review notifications are connected' give prerequisites and an availability gate, which is real usage context. However, there is no explicit when-to-use-this-instead-of-X guidance (e.g., versus get_quote or create_quote), leaving the choice to inference.

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