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

The description discloses the bulk execution capability, which is a behavioral trait beyond the schema. However, it doesn't mention important behaviors like irreversibility of deletion, potential cascading effects on associated resources, or permission requirements. The annotations already indicate destructiveHint=false and readOnlyHint=false, so the description should provide more context on the destructive nature, but it only adds the bulk support note.

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 extremely concise: two short sentences. It front-loads the primary action and adds a key feature (bulk support). No wasted words, but it could benefit from more useful information.

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 tool with zero schema description coverage and no output schema, the description is inadequate. It provides the basic purpose but fails to explain the parameters, prerequisites, effects on related resources, or expected behavior on failure. The tool is relatively simple but the description should at least clarify the difference between voice_id and voice_ids usage.

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 description coverage is 0%, and the description does not explain any of the three parameters. It mentions 'voice_id' in the text but doesn't elaborate on the 'account' parameter or 'voice_ids' array semantics beyond the mention of bulk support. The description should compensate for the lack of schema descriptions by explaining parameters, but it does not.

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: 'Deletes a voice by its ID.' It identifies the resource (voice) and the operation (delete). It distinguishes from siblings by being specific to deleting a voice, though it could differentiate from other delete* tools that target different resources.

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 implies usage in the context of voice management, but it doesn't provide explicit guidance on when to use this tool versus alternatives like elevenlabs_delete_sample or elevenlabs_delete_finetune. It mentions bulk support but doesn't elaborate on when batch deletion is appropriate.

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