spotify-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Follow' implies a mutating operation, the description does not clarify idempotency (whether calling twice on the same user is safe), error handling for invalid IDs, rate limits, or the structure of the output schema.

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 single-sentence description is appropriately front-loaded with the core action. While efficient, its extreme brevity contributes to information gaps given the lack of supporting schema documentation or annotations.

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?

For a single-parameter mutation tool with an output schema, the description provides the minimum viable context to understand the tool's function. However, the combination of zero schema coverage and no annotations leaves critical gaps regarding parameter format and behavioral side effects that the description fails to address.

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?

With 0% schema description coverage, the description must compensate for the lack of parameter documentation. It minimally implies that 'user_ids' refers to Spotify user identifiers through the phrase 'Spotify users,' but fails to specify ID format (Spotify ID vs URI), maximum batch size, or how to obtain valid IDs.

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 specific action (Follow) and target resource (Spotify users), including scope (one or more). However, it does not explicitly differentiate from sibling tools like 'spotify_check_following_users' or 'spotify_follow_artists', though the distinction is implied by the resource name.

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 alternatives (e.g., when to use 'spotify_follow_artists' instead), nor does it mention prerequisites such as requiring valid Spotify user IDs or authentication requirements.

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