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

Annotations only declare safety/idempotency hints; the description adds the paid-credit reservation model, the returned operation_id plus async polling requirement, the required action scope for auth, the sandbox-simulation note, and the crucial caveat that blocked retrieval or timeout cannot prove removal. This is exactly the behavioral context annotations cannot carry, with no contradiction of readOnlyHint=false or idempotentHint=true.

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?

Purpose is front-loaded and the description is dense with useful facts, but the polling guidance ('poll get_operation for results') is stated twice and the paragraph hops between prerequisite, returns, cost, auth and environment, slightly diluting structure. Minor redundancy rather than real bloat.

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 paid, asynchronous, quote-gated tool with no output schema, the description covers the return fields, the cost/credit model, the async polling path, the auth scope and the interpretive caveat. An agent has everything needed to call it and interpret the result correctly.

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 both parameters (quote_id, idempotency_key) are fully documented in-schema, so baseline 3 applies. The description does add that the quote must come from create_quote(action='status') and that all task input lives in the quote, but it adds no syntax or conflict semantics beyond what the schema already states.

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 ('Fetch a fresh content observation for an existing case') and immediately distinguishes itself from siblings by contrast: get_case reads stored observations, get_operation polls queued work. An agent can identify the tool's role without opening any 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?

Gives an explicit prerequisite flow (create_quote with action='status' and the required input fields), names the free alternatives (get_operation, get_case) and the condition selecting them, and flags the tool as paid network work. Nothing is left to inference.

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