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

Annotation contradiction: destructiveHint=false while the description says 'Deletes a dubbing project,' implying destructive behavior. The description also fails to disclose permanence, reversibility, or side effects beyond the stated action.

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 sentences, front-loaded with the main purpose, and the bulk support sentence adds useful information without redundancy. It is concise and readable, though sparse on details.

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 delete operation with conflicting annotations, a similarly named sibling, and an undocumented required parameter, the description is too thin. Missing permanence, alternative selection, and parameter relationship details.

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%, so the description must compensate. It only explains dubbing_ids via 'bulk support,' leaving dubbing_id and account undefined, including whether dubbing_id is still required for bulk calls.

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?

Description states 'Deletes a dubbing project' with a specific verb and resource. However, it does not distinguish itself from the sibling 'elevenlabs_dubbing_project_delete', which appears to perform the same operation, preventing a top score.

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 like elevenlabs_dubbing_project_delete. The bulk support note hints at a use case but does not explain when to choose batch vs single deletion.

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