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

Goes well beyond the annotations: it discloses that exactly the quoted credits are spent, that the quote must belong to the connected account and match price/request/expiry, and that failed work is refunded. The refund-on-failure guarantee and the single-use nature of quotes are the details an agent could not infer from destructiveHint/openWorldHint alone.

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?

One dense sentence that front-loads the action ('Start a quoted iter0 request') before the precondition and the validation/refund details. Every clause carries operational weight — nothing is restated from the title or schema.

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?

An output schema exists so return values need no explanation, and the description covers the remaining risks for a destructive, credit-spending tool: validation checks, exact charge amount, and refund behavior. Nothing an agent needs to call it safely is missing.

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 only 25%, so the description carries most of the burden: it names all four fields and stresses they must be passed 'unchanged' from the quote, which the schema cannot express. It does not explain the shape of the nested arguments object or credit precision, so a small gap remains.

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 ('Start a quoted iter0 request') and positions itself in a two-step quote-then-confirm flow, which no sibling tool occupies. The schema enum names the three dispatched operations, so an agent can see exactly what work is being triggered.

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 precondition — only after 'the person has confirmed its price' — which is the key gating rule an agent needs. It does not name alternatives (e.g., re-quote instead of reusing an expired quote), so it falls short of full when/when-not routing.

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