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 and successfully discloses the 50-track limit, ordering preservation ('in order'), and device dependency. It could improve by mentioning error behavior (e.g., what happens if >50 URIs are provided) or noting the output format, but covers the essential safety/constraint profile.

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 exactly two efficient sentences with zero redundancy. Critical information (action, limit, ordering, device requirement) is front-loaded and immediately accessible.

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 (relieving the description of return value documentation duties) and only one parameter, the description is sufficiently complete. It successfully captures the unique constraints (50-track limit, device requirement) necessary for correct invocation, though URI format details would strengthen it further.

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?

The schema has 0% description coverage for the 'uris' parameter. The description implies the parameter contains track URIs via 'Add multiple tracks' and constrains it with 'max 50', but does not specify the expected URI format (e.g., 'spotify:track:xxx') or that the array must contain valid Spotify track identifiers.

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 specific action ('Add multiple tracks'), target resource ('playback queue'), and key constraints ('max 50', 'in order'). The 'max 50' and plural 'tracks' effectively distinguishes this batch operation from the likely single-track sibling 'spotify_add_to_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 a critical prerequisite ('Requires an active device') but does not explicitly contrast this tool with siblings like 'spotify_add_to_queue' (single track) or 'spotify_queue_from_playlist' (playlist-based). Users must infer the batch vs. single distinction from the name and 'multiple tracks' phrasing.

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