delete_transcript

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

The description adds value beyond the schema by revealing that deletion removes associated files (txt, json, md). No annotations exist, so description carries full burden. It doesn't discuss reversibility or permissions, but the behavior is clear.

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, front-loaded with action and scope. No wasted words; every sentence provides necessary 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 simple deletion tool with two parameters and no output schema, the description is largely complete. It covers the main effect (file removal) but omits mention of return values or error handling. Still adequate.

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%, so the description does not need to elaborate on parameters. It reinforces the video_id purpose indirectly. The description adds no extra param details, but that is acceptable given full schema coverage.

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 clearly states the action (delete), the resource (specific transcript by video ID), and the scope (removes associated files). It distinguishes from siblings like delete_all_transcripts and cleanup_old_transcripts.

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 description implies when to use (delete a specific transcript) but does not explicitly state when not to use or mention alternatives like delete_all_transcripts. Context from sibling names helps, but lacks direct guidance.

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