spotify-mcp

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

With no annotations provided, the description carries full burden. It successfully discloses the output content (artist, album, duration) and format (text list), but omits whether this creates persistent files, requires specific auth scopes, or has rate limiting implications. Mention of output schema existence reduces burden, but behavioral traits beyond format are missing.

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, dense sentence with zero waste. Information is perfectly front-loaded: verb ('Export'), scope ('playlist'), and format details ('formatted text list with...') appear immediately. Every clause 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?

Appropriate for a simple, single-parameter tool with an output schema. The description adequately covers the export functionality without needing to detail return values (handled by output schema). Minor gap on parameter semantics prevents a 5.

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% (playlist_id has no description), and the description fails to compensate. While 'Export a playlist' loosely implies the parameter's purpose, there's no explicit mention of playlist_id, its format (Spotify URI vs ID), or constraints. Single-parameter tools have lower bars, but 0% coverage requires explicit parameter documentation.

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: states the action (Export), resource (playlist), and exact output format (formatted text list with artist, album, and duration). Clearly distinguishes from sibling spotify_get_playlist_tracks by emphasizing the formatted text output versus raw data retrieval.

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 choose this over alternatives like spotify_get_playlist_tracks or spotify_get_playlist. While the format description implies use cases (human-readable export), it doesn't state prerequisites, exclusions, or comparative scenarios.

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