Recent episodes of one show

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

Annotations already mark this as read-only, idempotent and non-destructive, so the description adds real value by explaining Apple's moving recent-window behavior and the limit caveat. It discloses data-source quirks rather than merely restating the operation. No contradiction with annotations.

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 with no filler: purpose, behavior caveat, and alternative are each front-loaded and distinct. Every sentence earns its place and the most important scoping information comes first.

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 simple list tool with fully documented parameters and a rich behavioral caveat, the description covers what the tool returns, how to request it, and when to choose a different tool. No output schema exists, but the 'recent episodes... newest first' statement gives sufficient return-context for invocation.

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% and the parameter descriptions already explain show formats, limit range, and storefront behavior. The description adds context about the feed URL for the alternative but no parameter-level detail beyond the schema, so the baseline 3 is appropriate.

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 a specific verb and resource: recent episodes for a show from Apple's catalog, newest first. It also distinguishes the tool from get_feed by clarifying this is the recent-window view, not the full back catalogue. The 'one show' framing separates it from cross-show siblings like list_recent_episodes.

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?

Explicitly states when to use this tool (recent window for one show) and when not to: 'For every episode a show has ever published, use get_feed with the feed URL from get_podcast.' It also warns that a short list is Apple's limit, not the show's history, which is actionable guidance for interpreting results.

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