spotify-mcp

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

With no annotations provided, the description carries full burden but discloses nothing beyond the basic read operation implied by 'get'. It omits authentication requirements, rate limiting, what constitutes 'detailed' information, or error behavior for invalid track IDs. The agent lacks context about whether this returns audio analysis, market availability, or just basic metadata.

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 structurally efficient and front-loaded, but its brevity crosses into under-specification. While concise descriptions are valuable, this one wastes its only sentence on generic phrasing that restates the tool name rather than adding specific value about the operation's scope or requirements.

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?

Despite having an output schema (reducing the burden to explain return values), the description remains incomplete due to zero parameter documentation and lack of behavioral context. For a tool with only one parameter, failing to document what a 'track_id' is or where to find it represents a significant gap that will likely cause invocation errors.

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%—the track_id parameter has no description. The description fails to compensate by explaining the expected format (Spotify URI vs. base62 ID vs. URL), providing examples, or clarifying where to obtain valid track IDs. It mentions 'track' generally but doesn't semantically map to the specific 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 states the basic action (get) and resource (track), but 'detailed information' is vague—it doesn't specify whether this includes audio features, metadata, popularity metrics, or availability. Crucially, it fails to distinguish from siblings like 'spotify_find_song' (search-based) or 'spotify_get_saved_tracks' (user library), leaving ambiguity about whether this performs a lookup by ID or a search.

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. Given siblings like 'spotify_search', 'spotify_find_song', and 'spotify_get_saved_tracks', the description should specify that this retrieves metadata for a specific track ID rather than searching by name or retrieving user-saved content.

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