search_podcasts

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

With no annotations, the description carries full burden. It discloses the return field downloads_per_episode and parameter usage rules. However, it does not mention pagination behavior, error states (e.g., empty query/filters), or read-only nature, leaving gaps.

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?

Three sentences: purpose, key return field, usage. Front-loaded, no redundancy, every sentence carries weight. Excellent conciseness.

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 5-parameter search tool with no output schema, the description covers main aspects: purpose, parameter constraints, and one return field. It references sibling tools for filter values. Lacks details on response structure beyond a single field, but schema documents parameters well.

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 100% (baseline 3). The description adds value by explaining filter syntax (comma-separated, full examples) and query syntax (parentheses, quotes, AND/OR, negation), which are not detailed in the schema. Mode and pagination are not elaborated, but overall adds meaningful context.

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 verb 'Search' and resource 'podcasts', and specifies the search dimensions (topic, title, publisher). It distinguishes itself from siblings like search_episodes by focusing on podcasts, and from list_* tools which are for filter values.

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?

Provides clear usage guidance: specify query or filters or both, with an example of filter syntax. References sibling tools for valid filter values. Does not explicitly mention when to use this vs search_episodes, but the context is implied.

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