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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds one genuinely useful behavioral caveat — segment clipping does not imply word-level alignment — which warns about timestamp precision. It is silent on pagination behavior despite having limit/cursor parameters.

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 tightly written sentences with the operation front-loaded and zero filler. The precision caveat is dense but earns its place; it could be slightly clearer about what 'segment clipping' refers to.

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?

The output schema covers return values, so that is not a gap. But a 7-parameter tool with zero required parameters and three competing identifier fields needs the description to explain selection and pagination, and it does neither — an agent could not reliably construct a call from this text alone.

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 coverage is only 29% (just start_ms and end_ms are documented, and only as inclusive/exclusive), so the description must carry weight and does not. Seven parameters including slug, video_slug, scene_id, limit and cursor are unexplained, and the description never clarifies the relationship between the three identifier parameters or how to paginate.

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 and resource (read timestamped voice transcript segments) plus a scoping mode (video window or scene). It does not distinguish itself from adjacent siblings such as get_text_track or get_audio_map, so an agent can't tell which to pick on name alone.

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 when-to-use or when-not-to-use guidance, and no mention of the alternatives (get_text_track, get_audio_map) an agent would weigh against it. The phrase 'video window or scene' hints at two access modes but never says how to choose between them.

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