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

With annotations already declaring read-only, idempotent, and non-destructive behavior, the description adds value by explaining the chunked/paginated nature ('bounded transcript chunk') and the continuation mechanism. No additional details like error handling are needed given the safety profile.

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 concise, front-loaded sentences. The first states the verb, object, and required parameters; the second gives the essential pagination instruction. No filler or redundancy.

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?

Given the rich schema and annotations, the description is nearly complete. It covers the core purpose and pagination. A minor gap is not explicitly directing users to sibling tools for obtaining GUIDs, but the schema does mention this, so the overall context is sufficient for a simple read-only paginated tool.

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 100%, with all parameters fully documented (e.g., cursor offset, max_chars bounds). The description adds no novel parameter info beyond mentioning show/episode GUIDs and next_cursor, which are already in the schema. Baseline 3 applies as schema does the heavy lifting.

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 uses a specific verb ('Fetch') and resource ('transcript chunk') with clear scope ('for a specific episode') and parameters ('show and episode GUIDs'). It distinguishes itself from sibling tools that list or search episodes, making the purpose unambiguous.

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 clearly indicates how to paginate ('Use next_cursor to continue reading'), which is key usage context. However, it does not explicitly state when to prefer this tool over siblings or provide exclusions; the differentiation is implied by the transcript-specific purpose.

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