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

No annotations are provided, so the description carries the full burden. It mentions ordering and optional filtering but does not disclose whether the operation is read-only, if authentication is required, or pagination behavior (e.g., the 'limit' parameter is described in schema but not in description). It adequately indicates a safe list operation but lacks some behavioral details.

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?

Two sentences, front-loaded with the action and key ordering detail, no wasted words. Efficient and to the point.

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 list tool with 2 parameters, the description covers the main purpose, ordering, and optional filter. Missing details like return format or pagination behavior, but schema covers 'limit' description. Sibling tools may hint at episode structure. Mostly complete.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema for 'limit' and only repeats the filtering role for 'podcast_slug'. No additional semantics are provided.

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 verb 'list' and the resource 'published episodes', specifies ordering from newest to oldest, and optionally filters by series, which distinguishes it from sibling tools like 'get_podcast_episode' (single episode) and 'list_podcast_series' (series).

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 implies use for listing multiple episodes with optional filtering, but does not explicitly exclude use cases or mention alternative tools like 'get_podcast_episode' for a single episode. Context is clear but lacks explicit when-not guidance.

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