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 successfully discloses the data source (your top artists) and key output traits (diversity scoring, niche detection), but omits mutation risks, caching behavior, or computational intensity of the analysis.

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, efficient sentence of 13 words with zero redundancy. Front-loaded with the action verb 'Build', followed by the resource, key features, and data source. Every phrase contributes essential information.

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 single-parameter analytical tool given the existence of an output schema (which handles return value documentation). However, the lack of parameter documentation and usage guidance leaves notable gaps for a tool processing personal data with temporal filtering options.

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 coverage is 0% for the time_range parameter, requiring the description to compensate. While 'from your top artists' loosely implies temporal filtering, the description fails to document the parameter's existence, valid values (short_term/medium_term/long_term), or default behavior.

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 builds a 'genre taste profile' with specific analytical outputs (diversity score, niche artist detection) and identifies the data source (top artists). It implies analytical depth beyond simple retrieval, distinguishing it from siblings like spotify_top_artists, though it doesn't explicitly name them.

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 on when to use this versus similar analysis tools like spotify_taste_evolution or spotify_listening_patterns. No mention of prerequisites (e.g., needing sufficient listening history) or when the analysis might be unreliable.

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