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. It successfully discloses the core behavioral trait (filtering for non-singles), but omits other critical behaviors like error handling when an artist has no deep cuts, rate limits, or whether results are randomized or sorted.

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 of 11 words with zero redundancy. The definition is front-loaded and every word earns its place.

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, the description appropriately avoids detailing return values. However, with 0% schema coverage and no parameter documentation in the description, the tool is under-specified for invocation despite the clear conceptual purpose.

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 'artist's deep cuts' implies an artist identifier is needed, the description fails to document the limit parameter or specify that artist_id expects a Spotify URI/ID rather than a human-readable name.

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 provides a specific verb ('Find'), resource ('artist's deep cuts'), and precise scope definition ('album tracks that were not released as singles'). This clearly distinguishes it from sibling tools like spotify_artist_deep_dive or spotify_discover_by_artist by defining the specific filtering logic used.

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 definition of 'deep cuts' implicitly signals when to use this tool (seeking non-single album tracks), but lacks explicit guidance on when to prefer this over spotify_artist_deep_dive or prerequisites like obtaining the artist_id.

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