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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important context beyond them: deletion is permanent, it removes both the stored transcript and its job, and it is free. It does not, however, discuss recovery, authorization, or failure behavior.

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?

The description is a single front-loaded sentence with no wasted words. The parenthetical clarification about what gets destroyed is compact and useful.

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 simple one-parameter destructive tool with rich annotations and no output schema, the description is nearly complete: it states permanence, what is deleted, and cost. The main missing piece is parameter guidance for transcriptionId.

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 0%, and the single required parameter 'transcriptionId' is not explained in the description. The phrase 'a finished transcription' implies what is being targeted but does not clarify the identifier's format, source, or usage.

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 and resource: permanently delete a finished transcription, and it clarifies scope by identifying the stored transcript and its job. This distinguishes it clearly from sibling read/list tools such as get_transcription and list_transcriptions.

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?

Usage is implied by the destructive verb and the qualifier 'finished transcription', but the description does not explicitly say when to use this versus alternatives, nor does it mention prerequisites or exclusions. It is adequate but lacks routing guidance.

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