Get a show's episodes

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds useful behavioral detail: episodes are sorted newest first, any show identifier form is accepted/detected, and each episode exposes its Podcasting 2.0 extras via a 'has' attribute. These go beyond the annotations without contradicting them.

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 sentences deliver the core purpose, ordering, identifier flexibility, payload hint, and a concrete usage recommendation. The most important facts are front-loaded, and no sentence is wasted.

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 three-parameter, one-required-parameter tool with no output schema, the description covers purpose, ordering, identifier formats, an important return attribute ('has'), and parameter selection guidance. It could be slightly stronger by explicitly noting the response is a list and how many episodes are returned by default, but the schema covers max, so the gap is minor.

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 already documents all three parameters with 100% coverage, so the baseline is 3. The description adds meaningful guidance beyond the schema by recommending 'since' over a large 'max' for recent episodes and by clarifying that the 'show' identifier form is auto-detected so callers should pass what they have without converting.

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 returns episodes for one show, newest first, and specifies that it accepts multiple identifier forms. It is distinguishable from siblings like get_episode (single episode) and get_recent_episodes (not tied to one show), though it does not explicitly name them.

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 clear context for using the tool and even provides internal guidance on preferring 'since' over a large 'max' for recent episodes. However, it never explicitly says when to prefer this tool over sibling tools such as get_episode or get_recent_episodes, leaving that to inference.

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