spotify-mcp

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

No annotations provided, so description carries full burden. Discloses the selection algorithm ('sampling related artists' catalogs'), which is valuable behavioral context. However, missing safety info: doesn't clarify if this creates a persistent playlist in the user's library or temporary state, or whether it's idempotent.

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 15-word sentence with zero waste. Front-loaded action ('Create'), immediately qualified with 'radio-style' distinction, and explains both input (seed) and mechanism (sampling catalogs). Every word earns its place.

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 3-parameter tool with output schema (so return values needn't be explained). Core function is clear, but completeness suffers from undocumented optional parameters (name, limit) given the schema provides no descriptions.

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 0%, requiring description compensation. Mentions 'seed track or artist' which maps to seed_uri, but completely omits documentation for 'name' (playlist name?) and 'limit' (track count?). With zero schema descriptions, leaving 2/3 parameters undocumented is a significant gap.

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?

Excellent specificity: 'Create' (verb), 'radio-style playlist' (resource), 'from a seed track or artist by sampling related artists' catalogs' (mechanism). Clearly distinguishes from generic spotify_create_playlist and discovery tools like spotify_discover_by_artist by specifying the radio algorithm approach.

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?

Implies usage through 'radio-style' (algorithmic, continuous listening), but lacks explicit when-to-use guidance versus close siblings like spotify_playlist_radio or spotify_discover_by_artist. No mention of prerequisites like needing a valid seed URI format.

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