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 explains the round-robin algorithm and the 2-5 playlist limit, but omits important behavioral details such as authentication requirements, whether original playlists are modified, and how unequal playlist lengths are handled (truncation vs. cycling).

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 single-sentence description is efficiently front-loaded with the core action. Every term ('round-robin', '2-5') provides essential, non-redundant information that helps distinguish this tool's unique behavior.

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 two-parameter tool with an output schema, the description covers the essential functionality and constraints. It appropriately focuses on the interleaving logic rather than return values (covered by the output schema), though it could improve by mentioning edge cases like empty source playlists.

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?

Given 0% schema description coverage, the description partially compensates by clarifying the '2-5 source playlists' constraint for the playlist_ids parameter. However, it fails to explicitly document the name parameter or explain the expected format/type of playlist IDs, leaving significant semantic gaps.

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 uses a specific verb ('Create'), identifies the resource ('new playlist'), and precisely defines the mechanism ('round-robin interleaving') and constraints ('2-5 source playlists'). It effectively distinguishes this tool from siblings like spotify_merge_playlists through the specific 'interleaving' terminology.

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?

While the 'round-robin interleaving' phrasing implies a specific use case (alternating tracks between playlists), the description lacks explicit guidance on when to choose this over alternatives like spotify_merge_playlists or spotify_create_playlist. No prerequisites or exclusions are stated.

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