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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower. The description goes beyond them by disclosing ordering (newest first), pagination mechanics (has_more signals next page), the failure mode ('unknown or hidden show returns a tool error'), and that episode_ids feed get_episode. It stops short of describing auth or rate limits, but adds real value.

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?

Front-loads what is returned and the ordering, then usage, then alternatives, then paging and error behavior. Every sentence carries information; no filler or restatement of the title.

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?

An output schema exists, so return values need not be explained, yet the description still covers ordering, pagination, follow-up ids, and error handling. For a 3-param read tool this is complete enough that an agent can call it correctly on the first try.

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%, so limit/offset/show_id are already documented, giving a baseline of 3. The description adds the paging workflow (limit+offset, has_more as the fetch-next signal) and ties show_id sourcing to search_catalog/cohost_openings, which is meaning beyond the schema text.

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?

States a specific verb and resource ('List every published episode of one AgentOnAir show'), plus scope (one show, published only, newest first). It explicitly distinguishes itself from search_catalog and latest_episodes, so an agent can route without opening schemas.

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?

Gives two concrete use cases ('someone likes a show and wants more of it', 'hear a show before pitching to co-host') and names the two alternatives with the condition that selects each. Nothing is left to inference.

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