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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds genuinely new behavior: the deletion is permanent and cannot be undone, but characters built from the voice keep working. That side-effect detail is not encoded in any annotation.

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 compact sentences. The destructive constraint is front-loaded ('Permanently delete'), followed by the consequence and the sibling routing. 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 two-parameter destructive delete with full schema coverage and annotations carrying the safety profile, the description covers what to pass, where the id comes from, what happens to dependent characters, and which sibling to use. Return values are not explained, but no output schema exists and a DELETE needs little description of its response.

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 coverage is 100%, so both parameters are already documented. The description explains where the id value comes from (vocal_id from mureka_list_vocals with mine: true), which adds sourcing guidance but no format or type detail beyond the schema. Baseline 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 states a specific verb and resource: 'Permanently delete a singing voice you uploaded'. It explicitly distinguishes this tool from mureka_delete_voice (which handles cloned speech voices), so an agent can tell the two delete tools apart without opening either schema.

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?

It tells the agent the precondition (a voice you uploaded, with vocal_id from mureka_list_vocals filtered to mine: true) and names the alternative tool for cloned speech voices. When-to-use and when-not-to-use are both explicit.

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