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

With no annotations, the description must carry behavioral disclosure itself. 'List' clearly indicates a read-only retrieval operation with no destructive side effects, which is good. However, it does not mention pagination, ordering, how `limit` behaves, or what the response contains, leaving some behavioral ambiguity.

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 compact and front-loaded: the first sentence states the tool's purpose, and the second resolves the key parameter ambiguities. There is no filler, repetition, or unnecessary detail.

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 filtered-list tool, the description covers the essential invocation knowledge: what the tool lists and what values the main parameters expect. It also points to `browse_catalogue` for obtaining a valid slug. The absence of any guidance on `limit`, pagination, or return format leaves minor gaps, but the core usage is 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?

The input schema provides no descriptions, so the description carries the full burden. It compensates well by enumerating the accepted values for `kind` and explaining that `slug` comes from `browse_catalogue`. The `limit` parameter, however, is never mentioned or explained, which prevents a perfect score.

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 begins with a specific verb and resource: 'List the episodes belonging to one podcast, topic, or guest.' This clearly scopes the tool to fetching episodes by a single entity and distinguishes it from broader search or single-episode tools like search_episodes and get_episode.

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 makes the intended use case clear: retrieve episodes for one podcast, topic, or guest. It also provides the key prerequisite that `slug` comes from `browse_catalogue`, which orients the agent on the correct workflow. It stops short of explicitly naming alternatives or exclusions, so it earns a 4 rather than a 5.

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