podcast_get_episodes

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

With no annotations, the description should disclose behavioral traits like authentication requirements or limits. It only says 'get episodes' without mentioning that api_key and api_secret may be needed for Podcast Index authentication, or that the response might be paginated. This is a significant gap for a tool requiring credentials.

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 a single short sentence, which is concise. However, it is too brief to cover necessary details for a tool with 4 parameters and no annotations, resulting in under-specification rather than concise completeness.

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?

Given the presence of 4 parameters, no annotations, and no output schema, the description should explain how to obtain the podcast ID, the role of max, and authentication requirements. It currently lacks this essential context, leaving the agent underinformed.

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 description coverage is 0%, so the description carries full burden. It provides minimal context (only implies id is a podcast identifier). The meaning of max, api_key, and api_secret is left entirely to inference, which is insufficient for correct invocation.

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 action (get episodes) and the resource (podcast from Podcast Index), specifying the source. However, it does not differentiate from sibling tools like podcast_recent_episodes or podcast_search_episodes, which could cause confusion about when to use this specific tool.

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 usage guidelines are provided. The description does not indicate when to use this tool vs alternatives such as podcast_search_episodes or podcast_by_feed_url, nor does it mention prerequisites like needing a podcast ID from a previous search.

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