get_episode_passages

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

Annotations already mark readOnlyHint=true and destructiveHint=false, and the description adds non-obvious behavior: overlapping passages, pagination by last end time, maximum 50 passages, and preservation of original wording. This exceeds what annotations provide and sets correct expectations.

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?

Three short front-loaded sentences with no filler. The core behavior is stated first, followed by pagination cap and output fidelity, each sentence earning its place.

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, 3-parameter tool with an output schema, the description covers the critical operational details: start time, pagination method, limit, and wording. The only notable gap is selection guidance among sibling tools, which is covered under usage guidelines.

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 coverage the description must carry parameter meaning. It maps 'at or after a time' to start_seconds and 'Maximum 50 passages' to limit, but it does not explicitly identify episode_id or explain how start_seconds and limit interact with pagination. Enough to get started, but not complete parameter guidance.

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 identifies a specific action ('Read') and resource ('surrounding transcript passages') with a clear temporal scope ('at or after a time') and notes overlapping passage behavior. It doesn't explicitly contrast with siblings like get_evidence or search_bike_evidence, but the resource/temporal scope makes the purpose recognizable.

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 no guidance about when to choose this tool over its siblings (search_bike_evidence, get_evidence, get_coverage, list_episodes). It provides pagination instructions, but no when-to-use or exclusion criteria.

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