podcast_search

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

With no annotations, the description must disclose behavioral traits. It does not mention that the tool likely performs a read-only search, nor does it indicate whether API keys are required for certain features or explain rate limits or pagination. The return format is not described.

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 extremely concise (one short sentence), which is positive for brevity but negative for completeness. It lacks structured information, though the single sentence is clear and front-loaded.

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 tool has 4 parameters (one required, three optional with no model descriptions), no output schema, and no annotations, the description is severely incomplete. It fails to provide essential context about the search behavior, output structure, or authentication requirements.

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?

The schema provides no descriptions for parameters (0% coverage), and the description does not add any meaning. Parameters like 'q', 'max', 'api_key', and 'api_secret' are left unexplained, leaving the agent without guidance on how to populate 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 (search) and the target resource (podcasts on Podcast Index). It differentiates from sibling tools like 'podcast_get_episodes' or 'podcast_trending' by specifying the search functionality. However, it could be more explicit about the scope (e.g., searching by title, host, etc.).

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 like 'podcast_by_feed_url' or 'podcast_search_episodes'. The description lacks any context about appropriate use cases or prerequisites.

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