spotify-mcp

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

No annotations provided, so description carries full burden. Claims 'List all' but limit parameter (default 50) suggests pagination is required for large discographies. Does not disclose authentication requirements or rate limits.

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 no redundancy. However, given zero schema descriptions and no annotations, the brevity leaves significant gaps that appropriate verbosity could fill.

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?

With 0% schema coverage and no annotations, the description inadequately documents the 3 parameters (particularly the required artist_id and pagination via limit). Output schema exists, mitigating need for return value description.

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%, requiring description compensation. Mentions content types (albums, singles, compilations) providing semantic context for include_groups, but fails to document artist_id requirements, limit pagination behavior, or valid include_groups values.

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?

Clear verb 'List' with specific resource types (albums, singles, compilations) and target (artist). Distinguishes from sibling spotify_get_artist (likely metadata) reasonably well, though could explicitly contrast with spotify_artist_deep_dive.

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 versus alternatives like spotify_artist_deep_dive or spotify_get_artist. No mention that artist_id must be obtained first (e.g., via spotify_search) or how to handle pagination.

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