sonic_delete_recording

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

The description only states the action without disclosing side effects, irreversibility, prerequisites, or error conditions. Since no annotations are present, the description carries the full burden of behavioral transparency, and it fails to provide any beyond the basic action.

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 a single, well-formed sentence with no fluff, making it efficient and easy to parse. It is appropriately front-loaded, but its brevity contributes to a lack of critical information. Overall, it is concise but not informationally robust.

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?

The tool is a simple deletion operation, but the absence of annotations and parameter explanation makes the description incomplete. It does not explain what 'temporary recording' refers to, when deletion is appropriate, or what the collect_ms parameter controls. While an output schema exists, that does not cover these usage questions.

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 schema defines a single optional parameter collect_ms, but the description does not mention it at all. With 0% schema description coverage, the description must compensate, and it does not. The meaning of collect_ms remains unexplained.

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') and the resource ('Sonic Pi's temporary recording'), providing a specific verb+resource pair. It does not explicitly distinguish from sibling tools like save_recording or record_file, but the qualifier 'temporary' adds some differentiation. Overall, it is clear and concise for the core purpose.

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?

No usage guidance is provided. The description does not indicate when to use this tool, what conditions warrant deleting the recording, or any alternatives. This leaves the agent without context for selecting it among the many recording-related sibling tools.

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