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 documents the time_range enum values (short_term/medium_term/long_term) and the maximum limit (50). However, it fails to disclose that this accesses personal listening data requiring specific auth scopes or what 'top' means (play count vs saves).

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, front-loaded with action verb, zero redundancy. Every clause provides essential information (function, parameter enum values, volume constraint) that is absent from the structured schema.

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 2-parameter read operation where output schema handles return documentation. However, marked down because accessing 'your' (personal) top artists requires authentication/authorization disclosure that is missing given zero annotations.

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?

Excellent compensation for 0% schema description coverage. The description documents the valid time_range string values that the schema omits, and 'up to 50' implies the limit parameter's maximum constraint. It could explicitly state the limit range (1-50) for a perfect score.

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 verb (Get), resource (top artists), and key constraints (time range options, up to 50). It distinguishes from the sibling 'spotify_top_tracks' by specifying 'artists' and implicitly differs from 'spotify_get_followed_artists' by using 'top' (listened) vs 'followed' (saved).

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 analytics tools like 'spotify_listening_patterns' or 'spotify_taste_profile'. No mention of prerequisites (e.g., user authentication required to access personal listening history).

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