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 batch limit (50), but fails to mention other behavioral traits like the read-only nature of the operation, the boolean array return format, or error handling for invalid IDs. The mention of the limit saves it from a lower score.

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 at two clauses: the action ('Check if you follow specific artists') and the constraint ('max 50 per call'). No wasted words, properly front-loaded with the verb.

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?

For a single-parameter tool with an output schema (relieving the description from explaining return values), the description is minimally adequate. However, given the 0% schema coverage, it should have explicitly documented the artist_ids parameter format and ID requirements rather than leaving it implied.

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%, so the description must compensate. While 'specific artists' implies the artist_ids parameter, it fails to clarify that Spotify Artist IDs (strings) are required versus artist names, or explain the array structure. The max 50 hint helps but doesn't fully document the parameter semantics.

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 action (check following status) and resource (artists), distinguishing it from siblings like spotify_check_following_users and spotify_check_saved_albums. However, it doesn't explicitly contrast with spotify_get_followed_artists (which retrieves the full list) versus this tool which checks specific IDs.

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 the important constraint 'max 50 per call' which guides batch sizing. However, it lacks guidance on when to use this versus spotify_get_followed_artists (bulk check vs. retrieving full library) and doesn't mention that Spotify IDs (not names) are required.

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