spotify-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a read-only operation, what the discovery algorithm entails, or any rate limiting. The term 'discover' is vague regarding whether it searches existing library content or recommends new tracks.

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 sentence with zero redundancy. The parenthetical mood examples are information-dense and front-loaded. No filler text or redundant restatement of the tool name.

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?

Adequate for a simple two-parameter tool with an output schema (which handles return value documentation). However, given zero annotations and 0% schema coverage, the description should have included behavioral safety flags and complete parameter documentation to be fully 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?

With 0% schema description coverage, the description partially compensates by listing valid mood values (happy, sad, energetic, etc.), effectively serving as enum documentation for the 'mood' parameter. However, it completely omits the 'limit' parameter, leaving half the parameter set undocumented.

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?

States specific action (discover) and resource (tracks) with clear mood-based categorization. The parenthetical examples (happy, sad, energetic, etc.) clarify the expected input domain. However, it does not explicitly differentiate from similar sibling tools like spotify_find_vibe_matches or spotify_discover_by_artist.

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 no guidance on when to use this tool versus alternatives (e.g., spotify_find_vibe_matches for vibe-based matching or spotify_genre_explorer for genre-based discovery). No prerequisites, exclusions, or workflow context is provided.

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