spotify-mcp

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

With no annotations provided, the description carries full disclosure burden but omits critical behavioral details: error handling when nothing is playing, whether data is real-time or cached, rate limits, or authentication requirements. It only lists the output categories without explaining behavior.

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?

Single sentence, nine words, front-loaded with the action verb. Zero redundancy or filler. Every word earns its place by identifying either the operation ('Get') or the specific data domains retrieved.

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 zero parameters and an output schema exists, the description adequately covers the return value categories (track, state, device) without needing to detail schema fields. Sufficient for tool selection despite lacking behavioral edge-case documentation.

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 input schema contains zero parameters, which per guidelines establishes a baseline of 4. The description correctly implies no filtering or input is needed by stating it gets 'the' currently playing track (singular, specific).

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 specific verbs ('Get') and resources ('currently playing track', 'playback state', 'device info'), clearly distinguishing this from playback control tools like spotify_play or spotify_pause. However, it doesn't differentiate from similar state-retrieval siblings like spotify_status or spotify_get_devices, which could cause selection ambiguity.

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 explicit guidance on when to use this tool versus alternatives (e.g., spotify_status for general player state or spotify_get_devices for device enumeration only). No mention of prerequisites like requiring an active Spotify session or what happens when nothing is playing.

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