podcast_search_episodes

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them — no note on authentication requirements despite api_key/api_secret parameters, no rate-limit or pagination behavior, and no indication of result shape.

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?

A single front-loaded sentence with no filler, but the brevity is under-specification rather than economy. It is appropriately sized only in the sense that nothing is wasted, not that enough is said.

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 an external open-world API tool with credential parameters, no output schema, and no parameter documentation, the description is far too thin. An agent cannot know how to authenticate or what the response contains without trial and error.

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% across four parameters, and the description compensates for none of it. It never explains what 'q' matches (episode title, description, person?), what 'max' bounds, or that api_key/api_secret are Podcast Index credentials.

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?

States a specific verb and resource: searching podcast episodes against the Podcast Index. It is clear what the tool does, but it never distinguishes itself from siblings like podcast_search, podcast_get_episodes, or podcast_recent_episodes, leaving the agent to guess which retrieval path applies.

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?

There is no guidance on when to choose this over podcast_search (shows) or podcast_get_episodes (episodes by feed), and no mention of the prerequisite credentials implied by api_key/api_secret. The agent must infer the selection rule from the name alone.

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