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 but discloses no behavioral traits beyond the implied read-only nature of 'Get'. It omits auth requirements, rate limiting, or error conditions (e.g., invalid artist_id). The output schema exists, so return values need not be described, but operational characteristics are missing.

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 efficiently structured without redundancy, but it is underspecified rather than appropriately concise. The brevity results in significant information gaps 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?

Given the 0% schema coverage and lack of annotations, the description is inadequate for agent use. While an output schema exists (covering return values), the complete absence of parameter documentation and sibling differentiation makes this insufficient for a tool with 80+ siblings where selection accuracy is critical.

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?

Input schema has 0% description coverage for the artist_id parameter. The description fails to compensate by not mentioning the parameter at all—no format guidance (Spotify ID vs URI), no example, and no explanation of how to obtain a valid artist_id. This leaves the critical input parameter completely undocumented.

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 (get detailed information) and resource (artist), but 'detailed information' is vague. It fails to differentiate from sibling tools like spotify_artist_deep_dive, spotify_artist_network, or spotify_get_artist_albums, leaving ambiguity about which artist-related data this tool specifically returns.

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 tool versus alternatives like spotify_artist_deep_dive (for comprehensive analysis) or spotify_get_artist_albums (for discography). No prerequisites or conditions are mentioned.

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