spotify-mcp

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

With no annotations provided, the description carries the full disclosure burden. It successfully adds behavioral context about sort order ('newest first') and pagination constraints ('up to 50'), but omits safety profile (read-only), authentication requirements, or error handling 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?

Single sentence efficiently packs three distinct pieces of information: the action, the sort order, and the maximum result constraint. Zero redundancy and front-loaded structure.

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?

Adequate for a simple read operation with two parameters, especially since an output schema exists to document return values. However, given 0% schema coverage and no annotations, the description lacks sufficient parameter documentation to be fully 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?

Schema description coverage is 0%, requiring the description to compensate. It implicitly references the limit parameter via 'up to 50' but provides no guidance on the required show_id parameter (format, where to obtain it, or examples).

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 clearly states the action ('Get episodes') and resource ('of a show'), distinguishing it from sibling tools like spotify_get_show (metadata) and spotify_get_episode (single episode). It effectively specifies the scope within the Spotify podcast domain.

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?

No explicit guidance on when to use this versus alternatives like spotify_get_saved_episodes (user's library) or spotify_get_show (show metadata). No mention of prerequisites such as needing a valid show_id from spotify_get_show or search.

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