spotify-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure but fails to mention mutation characteristics, authentication requirements, whether the action affects playback state immediately, or what the output schema contains.

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 appropriately brief for a simple action, but given the lack of parameter documentation and behavioral context, this brevity constitutes under-specification rather than efficient communication.

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?

Despite low complexity (one optional parameter), the description is incomplete. It fails to document the device_id parameter or explain playback control semantics, leaving critical gaps for an agent attempting to invoke the tool correctly.

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?

Schema description coverage is 0% (device_id lacks a description field), and the description makes no mention of the parameter, its optional nature, or what device ID format is expected. Complete failure to compensate for schema gaps.

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 states the basic action ('Skip to the previous track'), but it essentially restates the function name (spotify_skip_previous) with minimal expansion. While it clarifies the resource ('track'), it lacks specificity about scope or behavior that would elevate it beyond tautology.

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 provided on when to use this versus alternatives like spotify_skip_next, prerequisites such as active playback, or failure modes (e.g., behavior when at the first track in a queue).

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