Voices Delete Voice

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

The annotations already flag destructiveHint=true, and the description adds the specific consequence of freeing a clone slot, which goes beyond the annotation. While it doesn't discuss permanence or error handling, the annotation covers the core destructive nature, and the description adds meaningful context.

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, front-loaded sentence that immediately names the action and resource, followed by a useful consequence. There is no filler or wasted words.

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 one-parameter delete operation with no output schema, the description covers the action and the primary side effect. It omits return-value details, but given the simplicity, annotations, and sibling context, it is adequately 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?

The input schema provides a complete description of the 'id' parameter ('Cloned voice ID (UUID)') with 100% coverage. The description merely restates 'cloned voice' without adding new parameter details, so a baseline score of 3 is appropriate.

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 resource 'cloned voice by id', making the tool's function unambiguous. It also distinguishes itself from sibling tools like voices_get-voice and voices_clone-voice by focusing solely on deletion.

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 'freeing a clone slot' provides clear context for when to use this tool: when a clone is no longer needed and the slot should be freed. However, it does not explicitly state when not to use it or mention alternatives, so it falls just short of top-tier guidance.

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