list_show_episodes

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses newest-first ordering, included fields, default prose format, canonical endpoint, and deprecated status. However, it states 'Default limit 20' while the schema documents max_results default as SPOTIFY_MCP_MAX_ITEMS or 50, a factual inconsistency that could mislead agents about actual default behavior.

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 with the core purpose, then adds routing and behavioral details in a few short fragments. The final 'Also covers: paged podcast episodes' is vague and somewhat redundant with 'Page one', but overall the text is efficient and scannable.

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 5-parameter read tool with no annotations and no output schema, the description covers ordering, fields, canonical endpoint, and default style. But it leaves gaps: how to request subsequent pages, market parameter usage, and error/empty behavior. The conflicting default limit further weakens completeness. Adequate, but not fully self-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 100%, so the baseline is 3, but the description adds little beyond the schema and introduces an error: 'Default limit 20' contradicts the max_results schema description (env var or 50). The 'concise' prose note simply restates the response_format default. This misinformation makes the description net negative for parameter understanding.

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 opens with a specific verb and resource — 'Page one show's episode list' — and adds ordering ('newest-first') and key fields ('duration and release date'). It distinguishes itself from get_show_episodes by explicitly labeling that tool as a deprecated alias, so an agent knows this is the canonical list operation.

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 gives a clear use case ('the browse view for a single podcast') and explicitly routes agents away from the deprecated get_show_episodes alias. However, it does not contrast with other episode-related siblings like show_episode_search or get_show_latest_episode, and lacks explicit when-not-to-use guidance.

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