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

Annotations already mark the tool as readOnly, idempotent, and non-destructive. The description adds useful batch-support behavior and indicates 'full detail' output scope, but doesn't describe return shape, pagination, or any other operational caveats. No annotation contradiction is present.

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 two short, front-loaded sentences with zero filler. 'Bulk support' is a meaningful addition and the structure makes the core purpose immediately visible.

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 five-parameter getter with no output schema, the description covers the core purpose and batch mode, and annotations handle the safety profile. It remains incomplete around the account parameter, singular-vs-array usage, and expected response shape.

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?

With 0% schema description coverage, the description must compensate, and it does partially by explaining that project_ids and language_ids enable batched execution. However, it leaves the account parameter unexplained and doesn't clarify the relationship between singular project_id/language_id and their plural array counterparts.

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 'Get Dubbing Language Target' and 'Full language-target detail', identifying a read operation for a specific dubbing language resource. It distinguishes itself from sibling list/create/delete tools through the verb and detail-level phrasing, though it doesn't explicitly name those alternatives.

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 gives clear context: fetch full language-target detail, with optional bulk execution via project_ids and language_ids. It doesn't explicitly explain when not to use this tool or compare it with elevenlabs_dubbing_language_list, so it stops short of full when/when-not guidance.

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