Get many podcasts at once

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds meaningful behavioral context beyond annotations: batching behavior, rate-limit sensitivity, and the endpoint's exclusive identifier type. No contradictions with annotations.

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 with no filler. Each sentence has a distinct job: stating what it does, guiding when to use it, and constraining the accepted identifier. The most important information (purpose and batching advantage) is 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?

For a simple one-parameter, read-only tool with rich annotations and full schema coverage, the description covers what, when, why, and the critical input constraint. The absence of an output schema makes the lack of return-format details acceptable; the agent has everything needed to call it 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?

The schema already provides 100% coverage for the single parameter, including the array limits and a description. The description adds extra semantic value by explicitly excluding feed ids and explaining why GUIDs are required, which prevents a common misuse even with the schema present.

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 states a specific verb ('Look up'), a clear resource ('many shows'), and the key identifier ('by podcast GUID'). It also distinguishes this tool from its sibling get_podcast by emphasizing the batch aspect ('in one request'), making its purpose unambiguous.

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?

It explicitly tells agents when to use this tool instead of the alternative ('instead of calling get_podcast in a loop whenever you have more than three or four') and explains why ('one request rather than one each, which matters against a rate limit and is far faster'). It also states a clear exclusion ('Only accepts podcast GUIDs, not feed ids'), preventing incorrect usage.

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