spotify-mcp

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

With no annotations provided, the description carries the full disclosure burden. It successfully explains data transformation behaviors (grouping by year, calculating career span, counting release types) but omits operational details like authentication requirements, rate limits, or error handling for invalid artist_ids.

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 is a single, dense sentence that front-loads the core action ('Map') and immediately specifies the output structure. No words are wasted; every phrase adds distinct information about the aggregation methodology.

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 the existence of an output schema, the description appropriately focuses on the data transformation logic rather than return values. However, with zero schema coverage for the single required parameter and no annotations, the description is incomplete regarding how to properly invoke the tool.

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 has 0% description coverage for the artist_id parameter, and the description fails to compensate by explaining what constitutes a valid artist_id (Spotify URI vs. ID), where to obtain it, or any formatting requirements. This leaves a critical gap despite the parameter name being somewhat self-evident.

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 'Map[s] an artist's full release timeline' with specific output characteristics (grouped by year, career span, release type counts). It effectively distinguishes from siblings like spotify_get_artist_albums (likely flat list) and spotify_artist_deep_dive (likely detailed metadata) by emphasizing chronological aggregation.

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 usage through its specificity (timeline analysis), but provides no explicit when-to-use guidance or comparisons to alternatives like spotify_get_artist_albums or spotify_artist_deep_dive. No prerequisites or exclusions are mentioned.

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