spotify-mcp

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions the active device requirement but fails to clarify whether this tool appends tracks to the existing queue, replaces the queue entirely, or how it handles the current playback state. It also doesn't mention rate limits or error conditions.

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 consists of two efficient sentences with no redundant words. The primary action is front-loaded ('Queue tracks'), followed by key options and requirements. 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?

For a playback-control tool with 3 parameters and an output schema, the description covers the critical prerequisite (active device) and primary functionality. However, gaps remain regarding the 'count' parameter and queue manipulation behavior (append vs. replace), which are essential for correct usage given the lack of annotations.

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 implying playlist_id ('from a playlist') and explaining shuffle ('optionally shuffled'). However, it completely omits the 'count' parameter semantics (number of tracks to queue), leaving a third of the interface undocumented.

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 ('Queue tracks') and source ('from a playlist'), distinguishing it from generic queue tools like spotify_add_to_queue. However, it doesn't explicitly differentiate from spotify_build_queue or clarify if this appends to or replaces the existing queue.

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 the critical prerequisite 'Requires an active device,' indicating when the tool can be used. However, it lacks guidance on when to use this versus spotify_add_to_queue or spotify_build_queue, and doesn't mention if the target playlist must be owned by the user or just followed.

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