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 discloses the batch size limit ('max 50 per call'), which is valuable behavioral context. However, it omits other relevant behaviors such as error handling for invalid IDs, authentication requirements, or the fact that this is a read-only operation.

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 a single, efficient sentence with no wasted words. The constraint '(max 50 per call)' is parenthetically appended without disrupting the flow, making it appropriately front-loaded and dense with information.

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 simplicity (single parameter) and the presence of an output schema, the description provides minimal viable context. However, with zero schema coverage, it should have explicitly documented the 'album_ids' parameter requirement and format to be complete.

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, so the description must compensate. While it implies input is required via the 'max 50' constraint, it fails to explicitly mention the 'album_ids' parameter, its expected format (Spotify IDs vs URIs), or that it is required. This leaves a significant documentation gap.

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 core action ('Check which albums are saved') and scope ('in your library'), distinguishing it from siblings like 'spotify_save_albums' or 'spotify_get_saved_albums'. However, it could be more explicit that this checks specific provided albums against the library rather than retrieving the full collection.

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 critical constraint 'max 50 per call', which informs batching strategy. However, it lacks explicit guidance on when to use this tool versus 'spotify_get_saved_albums' (which retrieves the library) or prerequisites like requiring valid Spotify album IDs.

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