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 of behavioral disclosure but offers only the minimal 'Add... to queue' statement. It fails to clarify whether this appends to the end, triggers playback if idle, requires specific OAuth scopes, or what error conditions might occur (e.g., invalid URI format).

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 is efficient and free of redundancy, front-loading the core action. While appropriately brief, its extreme conciseness contributes to the gaps in behavioral and parameter documentation given the lack of supporting schema metadata.

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 state-modifying tool with zero schema coverage and no annotations, the description is insufficient. It lacks URI format examples, behavioral side effects, and differentiation from similar queue-manipulation tools. While an output schema exists (reducing the need for return value documentation), the input and behavioral gaps remain significant.

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 provides crucial value by constraining the 'uri' parameter to 'track or episode' types, preventing the agent from attempting to queue albums, artists, or playlists. However, it omits the expected URI format (e.g., 'spotify:track:xxx') which would be necessary for correct invocation.

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 identifies the action ('Add') and target resource ('playback queue'), specifying that it handles 'track or episode URI' inputs. However, it stops short of explicitly distinguishing this single-item addition from sibling tools like 'spotify_build_queue' or 'spotify_queue_from_playlist' that likely handle bulk operations.

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 guidance is provided regarding when to prefer this tool over alternatives such as 'spotify_play' (which might start immediate playback) or the other queue-building siblings. There are no prerequisites mentioned, such as requiring an active Spotify device or authenticated session.

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