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 fails to mention side effects (changing playback state), error conditions (if nothing is paused), authentication requirements, or the structure of the output schema which exists but is undocumented.

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 three-word description is extremely efficient with no filler, though it errs on the side of under-specification. Every word earns its place, but the extreme brevity leaves significant gaps in the information required for proper tool invocation.

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 0% schema coverage, lack of annotations, existence of an output schema, and numerous sibling tools with similar functionality, the description is inadequate. It fails to document the parameter, explain return values, or clarify edge cases (e.g., resuming when already playing).

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 'device_id' parameter, and the description adds no information about what this parameter represents (e.g., a Spotify device ID), how to obtain it (likely via 'spotify_get_devices'), or the behavior when omitted (likely uses active device).

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 core action (resume) and target (paused playback), distinguishing it from siblings like 'spotify_pause' (which stops) and implying a difference from 'spotify_play' (which starts fresh). However, it could explicitly clarify the distinction from 'spotify_play' for complete clarity.

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 no guidance on when to use this tool versus alternatives like 'spotify_play' or prerequisites such as having an active device or paused content. It omits critical context that would help an agent decide between resuming existing playback or starting new playback.

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