find_podcast

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

Describes return format, empty vs multiple entries behavior, and how to use returned id with other tools. No annotations provided, but description fully covers behavioral aspects.

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?

Five sentences, each essential. Front-loaded with purpose. No wasted words.

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?

Completely explains what the tool does, how to use it, and what to expect. Since no output schema, return format is described. Mentions integration with sibling tools.

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%, but description adds critical guidance: mutual exclusivity of parameters and that feed_url/youtube_channel_id may return multiple. Goes beyond 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?

Clearly states the tool finds a Rephonic podcast from an external identifier (Apple/iTunes, Spotify, YouTube, RSS). Distinguishes from sibling search_podcasts by specifying it uses direct identifiers, not text search.

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?

Explicitly says when to use (when you have an identifier) and when not to search first. Instructs to pass exactly one parameter. Names alternative tool (search_podcasts).

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