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 key behavioral trait of comparing across three distinct time ranges ('short, medium, and long term'). However, it lacks disclosure of other behavioral aspects like data freshness, caching behavior, or specific time range definitions that would help an agent understand operational constraints.

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 description consists of a single, efficient sentence (13 words) with zero waste. It is front-loaded with the action verb 'Compare' and packs essential context (resources, timeframes, purpose) into a tight structure where every word earns its place.

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?

Given that the tool has no input parameters and an output schema exists (covering return values), the description adequately covers the conceptual purpose. It could be enhanced by specifying the exact time range definitions (e.g., 4 weeks/6 months/lifetime) or noting authentication requirements, but it is sufficiently complete for agent selection.

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?

The input schema contains zero parameters, establishing a baseline score of 4. The description appropriately focuses on the tool's behavior rather than parameters, and no parameter clarification is needed since the schema is empty.

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 provides a specific action ('Compare'), clear resources ('your top artists and genres'), and scope ('across short, medium, and long term'). It effectively distinguishes from siblings like 'spotify_top_artists' (which likely lists without comparing) by emphasizing trend identification across time windows.

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?

The description implies when to use the tool ('to identify taste trends'), suggesting its analytical purpose. However, it fails to explicitly contrast with similar siblings like 'spotify_taste_profile' or 'spotify_listening_patterns', leaving ambiguity about which tool to choose for specific analysis needs.

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