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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: result ordering, cursor-based pagination, a truncation edge case where more episodes exist than the API can page to, and a per-call cost of 1 credit. That cost and truncation disclosure is exactly the kind of context annotations cannot carry.

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?

Four short sentences, front-loaded with the resource and ordering, then pagination, then the cost note last. The only waste is the opening fragment 'Podcast episodes.', which merely restates the title and the tool name before the useful sentence arrives.

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 names two response fields (`cursor`, `hasMore`) and explains their failure mode, which is more than most list tools offer. What remains uncovered is the shape of an episode object and the meaning of `limit`/`cache_max_age`, but for a straightforward paginated listing this is close to sufficient.

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 60%, so `id` and `cursor` are documented structurally; the description reinforces cursor semantics by tying it to 'the previous response.' But `limit`, `market`, and `cache_max_age` receive no explanation in either place, and the description does not compensate — no max limit, no statement of what market changes for episode availability.

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 second sentence states the resource precisely — episodes belonging to a Spotify podcast — and adds an ordering guarantee (newest first) that an agent can rely on. It is clearly not the show-metadata tool (spotify_podcast) or a search tool, though it never names those siblings explicitly, so the differentiation is inferential rather than stated.

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?

There is solid guidance for using the response (pass `cursor` from the previous response to page) and for the terminal condition (`hasMore` true with null `cursor`). However, there is no guidance on when to choose this tool over spotify_podcast or spotify_search, so the selection decision is left implied.

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