podcast_search

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

The description only indicates a read operation ('search'), but does not disclose authentication requirements (api_key, api_secret), rate limits, or what the response contains. Without annotations, the description carries the full burden and falls short.

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 sentence, which is too terse. While concise, it lacks essential detail, making it under-specified rather than efficiently informative.

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 4 parameters, no annotations, and no output schema, the description should provide context about the API, authentication, and expected results. It fails to do so, leaving the agent with insufficient information to use the tool correctly.

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 0% meaning no parameter descriptions exist, and the tool description does not explain any of the four parameters. The meanings of 'q', 'max', 'api_key', and 'api_secret' are left completely implicit.

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 (search) and resource (podcasts on Podcast Index). It is distinct from sibling tools like podcast_search_episodes or podcast_trending, though it could explicitly mention that it searches for podcast shows rather than episodes.

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 over alternatives like podcast_search_episodes or podcast_trending. There is no mention of prerequisites or context for invocation.

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