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

Annotations indicate read-only and idempotent. The description adds that the window is at most five minutes, defaults to 00:00-03:00, and returns exact timestamps. This provides behavioral context beyond annotations.

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, short but the first sentence is grammatically awkward. Could be more direct. No critical information is missing, but structure could be improved.

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?

Output schema exists, so return values are covered. However, the description does not explain what 'turns' means, how the window is specified, or the response limit. For a tool with 0% parameter coverage and 3 params, the description is incomplete.

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 mentions an 'optional window' but does not name or explain start_ms/end_ms or the episode parameter. The max window length hint is helpful but insufficient.

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 states it retrieves transcript turns within a time window with timestamps, but the phrasing 'overlapping an optional window' is awkward and unclear. It does not differentiate from sibling tools like get_clip or get_episode, but the tool name implies segment retrieval.

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?

Only mentions default window and response limits. No explicit guidance on when to use this tool versus alternatives, nor any prerequisites or constraints for the episode parameter.

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