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

Annotations already indicate read-only and non-destructive behavior. The description adds transparency about pagination (max 120,000 chars, has_more pattern) and notes Claude's character cap. It does not mention error cases for incomplete episodes or response format, but the provided context is solid.

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 compact and well-structured, with the purpose front-loaded, followed by pagination details and an alternative tool suggestion. Every sentence adds value without 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?

For a paginated tool, the description covers all critical aspects: what it fetches, pagination mechanics, character limits, and when to use alternatives. It lacks details on error handling or response structure, but given no output schema, this is sufficient for basic use.

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?

The schema describes offset and max_chars with details, but episode_id lacks a description. The description adds contextual meaning to parameters through usage examples (e.g., using offset from prior page), but does not explicitly define each parameter. With 67% schema coverage, the description moderately supplements but does not fully compensate.

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 clearly states the tool fetches transcript text for a completed episode, using a specific verb and resource. It distinguishes itself from the sibling tool search_transcription, making its 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 provides explicit guidance on when to use this tool (full transcript retrieval) and when to prefer the alternative search_transcription (focused look-up). It also explains pagination handling with clear instructions on using offset for subsequent calls.

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