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

Annotations already declare read-only and idempotent behavior, and the description adds valuable context by mentioning the return of progress status and batch execution via dubbing_ids. This goes beyond the structured annotations, offering specific behavioral details.

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 compact, consisting of two short sentences. It front-loads the primary purpose and then adds the batch support detail, with no unnecessary words or repetition.

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 read-only metadata getter, the description covers the core purpose and batch capability, but does not specify what metadata is returned beyond progress status, nor does it explain all parameters. It lacks details on output structure and alternative use cases, making it adequate but not thorough.

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 input schema has zero description coverage, so the description must explain all parameters. It only explains dubbing_ids for batch execution, omitting any details about dubbing_id (the required parameter) and account. The tool name implies dubbing_id is the identifier, but no explicit semantics are provided.

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 that the tool retrieves metadata about a dubbing project, including progress status. It specifies the verb 'Get' and the resource 'dubbing project', and the mention of bulk support further differentiates it from other dubbing-related 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?

The description provides no guidance on when to use this tool versus alternatives like elevenlabs_list_dubs or elevenlabs_dubbing_project_get. It only hints at bulk support, but does not explicitly state when to prefer this over other tools or any exclusions.

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