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

With no annotations, the description carries the full burden and excels: it discloses deterministic pagination (truncated: true, next_offset), instructs to concatenate content_md until next_offset is null, and explains lang is an output edition, not a filter, with lang_fallback behavior. This goes far beyond what a schema conveys.

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 dense sentences, each earning its place: the first states the core action, the second explains the pagination protocol, and the third clarifies lang semantics and size warning. Front-loaded with 'Read one section', no filler or repetition of schema details.

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 tool with 5 parameters, no output schema, and pagination complexity, the description is remarkably complete. It explains the return fields (truncated, next_offset, content_md), paging mechanics, section size differences, and lang fallback, covering everything an agent needs to invoke and process results correctly.

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 100% with solid per-parameter descriptions, so the baseline is 3. The description adds meaningful semantics beyond the schema: it explains the paging contract between offset, next_offset, and content_md, and clarifies the lang fallback behavior for transcripts, which the schema only hints at.

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 opens with 'Read one section of an episode', a specific verb+resource that clearly distinguishes this from sibling tools like lists, search, and download links. It also specifies the section types (tldr, digest, transcript) and the episode slug parameter, leaving no ambiguity about scope.

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?

It gives explicit guidance to 'Prefer tldr or digest' and warns that a transcript can exceed 100,000 characters and is rarely worth paging in full. While it doesn't directly contrast sibling tools, it clearly advises on section selection and warns against requesting a different lang for transcripts, providing practical when-to-use and when-not-to-use context.

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