cleanup_transcript

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

With no annotations, the description carries the burden of revealing destructive behavior. It states 'Delete the transcript file completely,' implying irreversibility. However, it doesn't mention any additional behavioral details like permissions, side effects on active transcription, or what happens to the file handle.

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 two short sentences, with the action front-loaded. Every word is functional; no filler.

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 parameterless deletion tool, the description is largely complete: it states the action, the object, and when to use it. The only notable gap is not addressing the potential confusion with clear_transcript, but given the explicit 'completely' and 'delete,' it may be sufficient.

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?

The tool has zero parameters, so the input schema provides no information. The description adds value by clarifying that the operation is a complete deletion rather than a reset, making the semantics clear. Baseline for 0 params is 4.

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 specific verb 'Delete' with the resource 'transcript file' and adds 'completely' to indicate permanence. It clearly states the action, though it doesn't explicitly distinguish from the sibling clear_transcript.

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 provides a clear usage context ('when you're done'), but it doesn't explicitly contrast this with clear_transcript or mention scenarios where this should not be used (e.g., if you only need to clear content without deleting the file).

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