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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are ordered newest first and each item carries title, duration, story count and audio URL, which tells the agent what a response looks like without an output schema. It leaves truncation/limit behavior and whether history exists uncapped unstated.

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?

A single front-loaded sentence that states the verb, the scope, the ordering, and the returned fields with no wasted clauses. Nothing could be removed without losing information.

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 two-parameter, non-destructive listing tool with no output schema, the description covers scope, ordering and result shape, which is close to everything an agent needs. The remaining gap is the limit/truncation story and any hint about paging to older 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 0%, so the description must carry parameter meaning. It clarifies that "show" selects one podcast from the enum and that the list is recency-ordered, but it never mentions the "limit" parameter, so the agent learns nothing about how many episodes are returned, the default of 10, or the maximum of 20 beyond what the schema's constraints state literally.

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 gives a specific verb and resource ("Lists recent episodes of one podcast show") plus ordering ("newest first") and returned fields, so an agent can tell this is a collection-listing tool. It does not explicitly contrast itself with the sibling get_episode (single episode) or list_shows, leaving that differentiation to inference from the names.

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?

Usage is only implied: "one podcast show" signals the show-scoped listing case and the sibling names hint that get_episode is for details. There is no sentence saying when to prefer this over get_episode or list_shows, and no note on the default limit or the 20-item cap when an agent needs more.

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