delete_voice

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

The description implies a destructive operation (delete) but does not disclose side effects, irreversibility, permissions, or rate limits. Since no annotations are provided, the description carries full burden and falls short.

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 very concise with one sentence and an Args line. However, the Args section largely repeats schema information, and the key purpose could be more front-loaded.

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 has a single required parameter and an output schema (though not shown). The description covers core behavior but lacks context on return values, side effects, or when it is appropriate to use given siblings.

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 description explains the single parameter 'voice_id' as 'the voice id to delete,' adding minimal context beyond the schema type. With 0% schema description coverage, it provides basic clarity but no format or source details.

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 'Delete a voice from your account,' using a specific verb and resource. It distinguishes the tool from siblings like 'delete_history_item' by the resource type, but lacks explicit differentiation from other deletion tools.

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 guidance is provided on when to use this tool versus alternatives (e.g., clone_voice, list_voices). There are no prerequisites, conditions, or exclusions mentioned.

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