delete_all_transcripts

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

With no annotations provided, the description fully bears the burden of disclosure. It clearly indicates destructive behavior ('Delete ALL') and irreversibility ('cannot be undone'). While it does not detail permissions or other side effects, the core behavioral trait is well communicated.

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: the first states the action, the second adds a caution. No redundant words, front-loaded with key information, and every sentence serves a purpose.

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 destructive tool with two parameters and no output schema, the description covers all essential aspects: the action, confirmation requirement, and optional directory. It could elaborate on what files are affected (e.g., 'transcript files'), but the context is generally complete.

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 baseline is 3. The description restates the schema's description for both parameters without adding new semantically meaningful information beyond what the schema already provides.

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 uses the verb 'Delete' with the specific resource 'ALL transcripts in the output directory', clearly distinguishing it from sibling tools like delete_transcript (single transcript) and cleanup_old_transcripts (older 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 warns 'Use with caution' and states irreversibility, implying when to use (only when certain of deletion). However, it does not explicitly state when not to use or provide alternatives, such as using delete_transcript for selective removal.

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