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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior: output is timed translated turns with 'review details', turns may target different languages, and it performs no speech synthesis. It omits cost/credit implications, error behavior, and how `context` or `formality` alter the result.

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?

Front-loaded with the core action, then segment requirements, then return shape and the synthesis exclusion. No filler sentences. Slightly compressed to the point of terseness on the undocumented top-level parameters.

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?

An output schema exists, so the return-value note is a bonus rather than a necessity. For a 6-parameter tool with zero schema documentation, however, half the parameters remain opaque in both the schema and the description, which is a real gap for correct 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?

Schema description coverage is 0% across 6 parameters, so the description must compensate. It usefully enumerates the per-segment fields (id, text, target_language, target_language_code, start_ms, end_ms, speaker_id), but leaves `context`, `speakers`, `formality`, `source_language` and `source_language_code` entirely unexplained, including valid formality values.

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?

States a specific verb+resource: localizing 'speaker turns together with shared dialogue context', which separates it from the plain `translate`/`translate_batch` siblings. The scope (multi-segment dialogue, per-turn target languages) is clear. It stops short of explicitly naming which sibling to use instead for single-string or file translation.

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?

Implies the intended workflow by requiring segments 'from transcribe_audio_detailed', and gives one explicit exclusion ('Does not synthesize speech', pointing away from synthesize_audio). It never states when to choose this over `translate_batch` or `localize_subtitles`, so the routing decision is left to inference.

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