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 appropriately discloses the 'public' scope twice, clarifying privacy limitations. However, it omits other behavioral details like error handling for invalid users, pagination behavior for large playlist lists, or rate limiting.

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 single sentence is front-loaded and free of redundancy. However, given the 0% schema coverage, the extreme brevity sacrifices necessary parameter documentation, making it slightly too terse for the complexity level.

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?

While the output schema handles return value documentation, the description inadequately covers the input side. With zero schema descriptions and no parameter explanation in the text, the description is incomplete for a tool that requires specific user identifier formats.

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% and the description fails to compensate. It does not explain the 'user_id' parameter format (whether it accepts Spotify URIs, usernames, or numerical IDs), leaving the agent without guidance on how to populate the required parameter.

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 it retrieves a user's public profile and playlists, using specific verbs and resources. It implicitly distinguishes from 'spotify_get_my_playlists' by targeting 'a Spotify user' (requiring an ID) rather than the authenticated user, though it could explicitly contrast with siblings.

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 provided on when to use this tool versus alternatives like 'spotify_get_my_playlists' (for current user) or 'spotify_get_playlist' (for specific playlist metadata). No mention of prerequisites like needing a valid Spotify user ID format.

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