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

Annotations declare destructiveHint=true, but the description usefully narrows what is actually destroyed: no transcription starts and the original upload remains available. That materially refines the destructive flag and tells the agent the operation is recoverable. It does not mention idempotency or whether the held price is released, so it stops short of a 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?

Two short sentences, outcome first, side effects second. No filler, though the second sentence packs two distinct facts that could be clearer.

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 and the operation's outcome is described, which covers the return-value gap. However, for a single-parameter mutating tool with 0% schema coverage, the complete absence of parameter semantics leaves a real hole an agent must guess around.

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?

The single parameter job_id has 0% schema description coverage, so the description must carry the burden and it does not mention job_id at all. The agent gets no guidance on what identifier is expected (quote id vs. task id vs. upload id).

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 (Cancel) and resource (the owned task's unconfirmed held price), which an agent can distinguish from confirm_transcription_quote or cancel_transcription. It does not explicitly name sibling tools, so it falls just short of the top score.

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 phrase 'unconfirmed held price' implies this applies only to quotes that were held but not confirmed, but the description never states when to choose it over cancel_transcription or confirm_transcription_quote. Usage is inferable rather than explicit.

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