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 of behavioral disclosure. It successfully clarifies the scope of data returned (genres, discography, related artists), but fails to address operational characteristics like whether this is a read-only operation, rate limits, data freshness, or how 'full' the discography is (all albums vs. selected).

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, efficient sentence front-loaded with the action verb 'Get'. While appropriately concise for a read operation, given the complete lack of schema documentation and annotations, the brevity comes at the cost of necessary parameter and behavioral context.

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 high complexity (80+ sibling tools, many overlapping in function), undocumented parameter, and lack of annotations, the description is incomplete. It does not clarify how this aggregating tool relates to more specific sibling tools, nor does it document the critical input parameter despite having an output schema to handle return value documentation.

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 schema has 0% description coverage for the 'artist_id' parameter. The description mentions 'artist profile' implying the parameter identifies an artist, but does not specify the expected format (Spotify URI vs. ID), where to obtain it, or provide an example. It fails to compensate for the undocumented schema.

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 retrieves a 'comprehensive artist profile' and lists specific data categories returned (genres, full discography, related artists). However, it does not explicitly differentiate from siblings like 'spotify_get_artist' (basic profile) or 'spotify_related_artists' (just related artists), leaving ambiguity about when to prefer this aggregated approach.

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 provides no guidance on when to use this tool versus the numerous sibling artist tools (spotify_get_artist, spotify_get_artist_albums, spotify_related_artists, spotify_artist_network). It does not mention prerequisites (e.g., needing a valid Spotify artist ID) or exclusions.

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