spotify-mcp

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

Without annotations, the description carries the full burden. It mentions results are 'ranked by overlap' which explains sorting behavior, and 'scan all your playlists' implies library scope. However, it omits performance characteristics, safety confirmation (read-only nature), or whether collaborative playlists are included.

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 14-word sentence that is front-loaded with the action verbs 'Scan' and 'find'. No redundant or wasted text; 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 existence of an output schema, the description appropriately omits return value details. However, for a tool with zero schema coverage on its two parameters, the description leaves a significant gap by not explaining parameter semantics or providing usage examples.

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?

With 0% schema description coverage (only titles 'Min Shared' and 'Owner Only'), the description must compensate but fails to mention either parameter. It should clarify whether 'min_shared' refers to track count or percentage, and what 'owner_only' filters.

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 scans playlists to find pairs with shared tracks and ranks them by overlap. However, it doesn't explicitly differentiate from the similar sibling tool 'spotify_find_playlist_subsets', though the mention of 'pairs' provides implicit distinction.

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 is provided on when to use this tool versus alternatives like 'spotify_playlist_compare', 'spotify_playlist_diff', or 'spotify_find_playlist_subsets'. The description only states what the tool does, not when to choose it.

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