spotify-mcp

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

No annotations provided, so description carries full burden. Discloses the 50-item limit (key behavioral constraint) and identifies target library ('Liked Songs'). Output schema exists so return value description is less critical, though auth requirements or rate limiting could be mentioned.

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 11-word sentence with zero waste. Front-loaded with action ('Check which tracks') followed by scope and constraint. Parenthetical limit placement is efficient.

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?

Appropriate for low complexity (1 param, boolean check operation). Output schema handles return values. Missing parameter documentation is the primary gap; otherwise covers purpose, resource, and batch limits adequately.

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 has 0% description coverage (parameter 'track_ids' has title but no description). Description mentions checking 'tracks' conceptually but fails to document the 'track_ids' parameter format, expected values (Spotify IDs), or that it must be an array. Insufficient compensation for schema 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?

Clear specific verb 'Check' + resource 'tracks in your Liked Songs' + scope constraint 'max 50 per call'. Distinguishes from sibling 'spotify_get_saved_tracks' (retrieval) and 'spotify_check_saved_albums' (different media type) through specific resource naming.

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?

Provides critical usage constraint 'max 50 per call' implying batching requirements, but lacks explicit when-to-use guidance versus alternatives like 'spotify_get_saved_tracks' or prerequisite context (e.g., needing valid track IDs).

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