podcast_recent_episodes

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

No annotations are provided. The description does not explain what 'recent' means, any limitations on episode count, authentication requirements implied by api_key and api_secret parameters, or any other behavioral traits.

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 is too sparse. Valuable space is wasted by not adding context about parameters or usage.

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?

With zero output schema, no parameter descriptions, and no annotations, the description is incomplete. It fails to inform the agent about return format, pagination, or authentication details, which are critical for a tool with optional auth parameters.

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% and the description adds no meaning to the parameters (max, api_key, api_secret). The agent cannot infer what 'max' controls or that api_key/api_secret are for authentication without external knowledge.

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 'Get recent podcast episodes from Podcast Index,' providing a specific verb and resource. However, without differentiating from sibling tools like podcast_get_episodes or podcast_search_episodes, it lacks precision.

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 given on when to use this tool versus alternatives. Sibling tools include podcast_get_episodes, podcast_search_episodes, and podcast_trending, but the description offers no context for selection.

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