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

Adds substantial context beyond the annotations: it names the collateral data destroyed (transcript, summary, translations), states irreversibility, and discloses the ownership authorization constraint. These are exactly the facts an agent needs before firing a destructive call.

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?

Three short sentences, destructiveness and irreversibility front-loaded before the usage constraint. Every sentence carries distinct information; nothing is repeated from the annotations verbatim.

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?

With rich annotations, a fully described single parameter, and an output schema handling return values, the remaining burden is behavioral nuance — destruction scope, irreversibility, ownership, and intent gating — all of which are present.

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 the id param already points at list_transcripts as its source. The description adds no further parameter guidance such as what happens with an invalid or already-deleted id, so baseline 3 applies.

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?

Specific verb (permanently deletes) plus an enumerated resource scope (recording, transcript, summary, translations). This clearly separates it from read/rename/export siblings, though no sibling is named explicitly as an alternative.

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 a genuine gating condition: call only when the user explicitly asks to delete a specific recording, which excludes speculative or automated use. It lacks a named fallback (e.g. rename_transcript or export_transcript) for the common 'user really wants X instead' case.

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