spotify-mcp

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

With no annotations provided, the description carries the full disclosure burden. It adds the Premium requirement (essential behavioral constraint) but omits details about playback continuity (does it resume/pause?), error states for invalid device_ids, or the effect of the force_play parameter.

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?

Extremely efficient two-sentence structure with zero filler. The Premium requirement is front-loaded as a hard constraint, and the action statement immediately clarifies the tool's singular purpose.

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 output schema exists, return values need not be explained. However, with 2 parameters and 0% schema coverage, the description should document the parameters and their interplay (device_id source, force_play behavior), which it does not.

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%, requiring the description to compensate. While 'device' implies the purpose of device_id, the description completely omits explanation of force_play (default false) or where to obtain valid device identifiers, failing to bridge the schema documentation gap.

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 (transfer playback) and target (different device), distinguishing it from playback control tools like spotify_play or spotify_pause which manage state rather than device location.

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 'Requires Premium' constraint provides critical prerequisite context, but the description lacks explicit guidance on when to use this versus alternatives, or the prerequisite workflow of obtaining device IDs (likely via spotify_get_devices).

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