spotify-mcp

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

No annotations are provided, so the description carries the full burden. It mentions the 'up to 50' constraint, hinting at pagination limits, but fails to disclose other behavioral traits such as authentication needs, caching behavior, or what the tool returns if the user follows no artists.

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 description is extremely concise at only five words. It is front-loaded with the action and contains no redundant or filler text. Every word serves a specific purpose in conveying the tool's function.

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's low complexity (one optional parameter) and the presence of an output schema, the description is minimally adequate. However, the complete lack of schema coverage for the parameter leaves a gap that the description only partially fills with the 'up to 50' hint.

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 schema has 0% description coverage for the 'limit' parameter. While the description mentions 'up to 50', implying the parameter's maximum value, it does not explicitly explain the parameter's purpose, default value (20), or that it controls the number of results returned.

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 tool retrieves the user's followed artists using the verb 'Get' and specifies the resource. The parenthetical '(up to 50)' provides useful scope constraints. However, it does not explicitly differentiate from siblings like spotify_top_artists or spotify_check_following_artists, which could cause confusion.

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 description provides no guidance on when to use this tool versus alternatives such as spotify_top_artists or spotify_get_artist. It omits prerequisites like authentication requirements and does not indicate what to do if the user wants more than 50 artists.

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