lookup_podcast

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

Discloses the tool is a lookup operation returning specific data types, but lacks explicit mention of read-only nature or any side effects. Since no annotations exist, the description carries full burden and is nearly sufficient.

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: first defines purpose, next two provide usage guidelines. No wasted words, front-loaded with key action.

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 no output schema, the description adequately outlines return types (metadata, chart rankings, latest episodes). Could mention data freshness or pagination but sufficient for agent understanding.

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?

Input schema has 100% coverage with a single parameter description. The description repeats the example but adds no new semantic information beyond the schema.

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?

Description explicitly states the tool retrieves podcast metadata, chart rankings, and latest episodes via Rephonic ID, and distinguishes from siblings by specifying when to use find_podcast or search_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?

Clearly instructs to use find_podcast for alternative IDs (Apple/iTunes, Spotify, YouTube, RSS) and search_podcasts if only the name is known, providing explicit when-to-use vs when-not-to-use.

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