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

No annotations are provided, so the description carries the full burden. It implies a read-only search operation (no mention of mutations), but it does not explicitly declare read-only behavior, rate limits, or side effects. The behavioral disclosure is minimal but acceptable for a simple search tool.

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 concise: two sentences front-loaded with the core purpose and return details. No unnecessary words or repetition, making it easy to scan.

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 output schema, and no annotations, the description provides clear purpose and return fields. It lacks context about pagination (limit parameter default and behavior) but is otherwise adequate for a straightforward search tool.

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 input schema has 75% coverage for parameter descriptions. The tool description adds no additional meaning beyond the schema for parameters; it only lists return fields. Since schema coverage is high, the baseline is 3, and the description does not improve parameter understanding.

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 explicitly states 'Search PitchIQ's podcast directory' with a specific verb (search) and resource (podcast directory). It lists return fields (title, host, listener tier, category, cover image) and distinguishes from sibling tools like search_creators and search_curators by focusing on podcasts.

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?

The description says 'Useful for finding podcasts an agent should pitch the user onto,' providing clear context for when to use the tool. However, it does not explicitly contrast with alternatives or state when not to use it, which could strengthen guidance.

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