podcast_search

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 that: it does not mention that api_key/api_secret may be required for authentication, nor any rate limits or pagination behavior tied to the `max` parameter.

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; every word earns its place and the verb/resource lead immediately. Its brevity is only a problem insofar as it leaves gaps covered under other dimensions.

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 a search tool with four undocumented parameters, no output schema, and crowded podcast siblings, the description is too thin. An agent cannot tell what is returned (feeds vs. episodes), how many results `max` permits, or whether credentials are mandatory.

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%, so all four parameters (q, max, api_key, api_secret) are undocumented. The description only implicitly suggests that the tool takes a query; it says nothing about the meaning of `max` (result limit?) or how the credential parameters should be supplied, leaving the description to do work it does not do.

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 clear verb and resource ("Search for podcasts") and names the data source (Podcast Index), so the agent knows what it does. However, it does nothing to distinguish itself from the sibling podcast_search_episodes, leaving ambiguity about whether it returns shows/feeds or individual 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?

There is no when-to-use guidance, no mention of alternatives such as podcast_search_episodes, podcast_by_feed_url, or podcast_trending, and no prerequisites. The agent must infer the appropriate context entirely on its own.

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