podcast_recent_episodes

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

No annotations are provided, so the description carries full burden. It does not disclose authentication requirements, limitations, pagination, or what 'recent' means. The input schema hints at authentication via api_key/api_secret, but this is not stated in the description.

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 concise sentence, but it lacks important details. While brevity is appreciated, the description is too sparse to be fully useful.

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 three parameters, no output schema, and multiple sibling tools, the description is severely incomplete. It does not explain the expected output, timeframe for 'recent', or authentication process, leaving significant gaps for an agent trying to use the tool.

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?

With 0% schema description coverage, the description must explain parameters. It fails to do so. The three parameters (max, api_key, api_secret) are not mentioned at all, leaving the agent without guidance on how to use them correctly.

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 recent podcast episodes') and the source ('from Podcast Index'). It uses a specific verb and resource, but does not differentiate from sibling tools like 'podcast_get_episodes' or 'podcast_search_episodes', which could cause confusion.

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 is provided on when to use this tool versus alternatives. Siblings such as 'podcast_get_episodes' (for a specific feed) and 'podcast_search_episodes' (for search) exist, but the description offers no information about the tool's intended use case or prerequisites.

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