get_show_episodes

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

With no annotations, the description carries the full burden. It discloses pagination and the resume-position scope requirement, which is useful. However, it does not mention the read-only nature, response format, or error behavior (e.g., invalid show ID). The added context is moderate but not comprehensive.

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?

Two concise sentences with the core purpose front-loaded. No fluff, and the scope note is relevant. Efficient use of space.

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 full schema coverage and no annotations, the description covers purpose and one authorization detail. However, it lacks usage guidance relative to sibling tools and any mention of output or error handling, leaving the agent to infer some calling context.

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%, so the parameters are fully documented in the schema. The description adds no additional parameter meaning beyond what the schema provides. Its mention of pagination is generic and does not clarify the limit/offset semantics further.

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 lists a podcast show's episodes and mentions pagination. It distinguishes from sibling tools like get_show (show details) and get_episode (single episode) even without explicitly naming 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?

No guidance on when to use this tool vs. alternatives. It does not mention that this is the tool for listing episodes of a show, or when to prefer get_episode for a single episode. The scope requirement is mentioned but not framed around usage selection.

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