List recent podcast episodes

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

The description adds the important behavioral constraint that the tool only works on podcast libraries, which is not covered by the readOnlyHint annotation. It also implies ordering by publication date. There is no contradiction with annotations, and the description provides context beyond the structured data.

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 extremely concise: two sentences that front-load the purpose and then add a critical constraint. Every sentence is meaningful and earns its place.

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?

The description is complete for a simple list tool with good schema coverage and annotations. It states the purpose, a key constraint, and the schema covers pagination and detail output. Without an output schema, the agent might infer the return format from the parameter descriptions, but the description could be slightly more explicit about the returned list of episodes.

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 the schema already describes all parameters well. The description adds value by stating the library must be a podcast library, which is a constraint on the library_id parameter not explicitly in the schema. The description does not repeat schema details, but it provides necessary context.

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 clearly states the tool lists the most recently published episodes across a podcast library, specifically the 'Newest Episodes' view. It uses a specific verb ('lists') and resource ('recent episodes'), and distinguishes itself from siblings like get_podcast_episode (single episode) and list_library_items (general items) by focusing on podcast-only recent episodes.

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 explicitly states a precondition: 'Only works on libraries with mediaType

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