spotify-mcp

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

No annotations are provided, so the description carries the full disclosure burden. It successfully indicates the content returned (now playing plus upcoming tracks), but omits behavioral details such as error states when no device is active, authentication requirements, or whether the queue persists across sessions.

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 is a single, efficient sentence that front-loads the action ('Get') and uses a parenthetical to clarify scope without wasting words. Every element 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?

Given the tool's simplicity (no inputs, read-only operation) and the presence of an output schema, the description adequately covers what the tool retrieves. It could be improved by mentioning error conditions (e.g., empty queue, no active device), but it meets the minimum viable threshold for completeness.

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 tool accepts zero parameters, which per the evaluation rubric establishes a baseline score of 4. The description appropriately focuses on the tool's behavior rather than inventing 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?

The description uses a specific verb ('Get') and resource ('playback queue') and explicitly scopes the output as 'now playing + upcoming tracks', which effectively distinguishes it from sibling tools like spotify_now_playing (likely current track only) and spotify_add_to_queue (mutation).

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 implies usage through the scope clarification (now playing + upcoming), but provides no explicit guidance on when to use this versus spotify_now_playing or spotify_build_queue, nor does it mention prerequisites like requiring an active playback device.

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