delete_custom_voice

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

Discloses irreversibility, unrecoverable deletion, and impact on saved voice_ids. No annotations present, so description carries full burden; covers key behavioral traits without mentioning potential restrictions or side effects.

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?

Four concise, well-structured sentences with no superfluous information. Each sentence adds value: action, irreversibility, consequences, user confirmation.

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?

Adequately covers deletion warnings for a simple tool with one parameter and output schema. Could mention permissions or soft delete but sufficient for safe invocation.

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?

Only one parameter (voice_id) with no schema description coverage. Description does not explain what voice_id represents or how to obtain it, relying solely on the schema's type requirement.

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 ('permanently delete a custom (cloned) voice') and resource, distinguishes from siblings like clone_voice or edit_custom_voice, and emphasizes irreversibility.

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?

Explicitly instructs to confirm with user before calling, warns about irreversibility and consequences. Does not explicitly state when not to use or alternatives, but direct instruction suffices.

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