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

Annotations already cover read-only, idempotent and non-destructive behavior, so the bar is lower. The description still adds useful context the annotations lack: the data is public, the exact result ordering (newest episode number first), and the returned field set.

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?

Three dense sentences, front-loaded with purpose and returned fields, with the ordering constraint placed last. The field enumeration is long but earns its place since there is no output schema; no filler text.

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?

With no output schema, the description usefully enumerates the returned fields and covers search, filtering and sort order. It omits pagination behavior/defaults (though limit/offset are in the schema) and never clarifies what 'the mapped collection' means or whether the collection is fixed.

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 the schema already documents q, limit, market and offset. The description restates q's search fields (title, slug, summary) and adds only a thin clarification that market filters 'the mapped collection', which is vague rather than additive. Baseline 3 applies.

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 (List) and resource (Creators & Cultural Icons podcast episodes) and even flags the visibility scope as public. It is clearly distinguishable from the sibling attic_get_episode (single item) by name and verb, but it never names or contrasts with any sibling explicitly.

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?

It explains what the optional q and market parameters do, which implies when to use them, but gives no when-to-use/when-not guidance and no alternatives (e.g. attic_get_episode for one episode, attic_search for cross-collection search). Usage is implied rather than directed.

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