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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value by enumerating exactly what is destroyed (uploaded file, transcript, all results) and framing it against the 24-hour auto-deletion window, which an agent could not infer from annotations alone. It does not describe failure behavior for already-deleted jobs, a minor gap given idempotentHint.

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 sentences, zero filler, with the destructive scope front-loaded and the 'Cannot be undone' warning closing it. Every clause carries information.

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 two-parameter destructive tool with full schema coverage, complete annotations, and no output schema, the description supplies what is needed: what is removed and the irreversibility. Only the post-success response shape and auth failure modes are unstated, both low-impact here.

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 100%, so both job_id (with format/pattern and provenance from transcribe_url or create_upload) and robot_key are already documented in the schema. The description adds no parameter-level meaning, which is acceptable at full coverage but leaves it at baseline.

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 (delete) plus the exact resources affected (uploaded file, transcript, all other results), and contrasts it with the default lifecycle (automatic deletion within 24 hours). No other sibling tool deletes jobs, so it is trivially distinguishable from get_job, list_jobs, and the transcription tools.

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 'right away, instead of waiting for the automatic deletion within 24 hours' gives a clear condition for choosing this tool over doing nothing. It stops short of explicit exclusions or prerequisites (e.g., only for jobs you own), but the usage context is unambiguous.

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