spotify-mcp

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

With no annotations provided, the description carries the full burden. It discloses the 50-item limit constraint, but omits other behavioral details like pagination support (whether offset/limit parameters exist), whether results include both owned and followed playlists, or auth requirements.

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 a single, efficient sentence with zero waste. Every word earns its place: the verb specifies the action, 'your' specifies the scope, and the parenthetical specifies the constraint.

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?

Given the tool has an output schema (covering return values), 1 simple parameter, and no nested objects, the description is minimally adequate. However, with zero annotation coverage and zero schema description coverage, it should ideally clarify the ownership scope (owned vs followed) and pagination behavior.

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% (the 'limit' parameter has no description field). The description partially compensates by mentioning '(up to 50)', which maps to the default value, but it does not explicitly name the 'limit' parameter, explain its optional nature, or describe valid ranges beyond the default.

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 (List) and resource (your playlists), and the parenthetical '(up to 50)' scopes the output volume. It distinguishes from sibling 'spotify_get_playlist' (singular) via the plural 'playlists' and possessive 'your', though it could explicitly contrast with fetching specific playlists.

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 provides no guidance on when to use this versus alternatives like 'spotify_get_playlist' (for specific playlist details) or 'spotify_get_playlist_tracks' (for contents). There are no prerequisites, exclusions, or contextual triggers mentioned.

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