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 identifies the operation as a mutation ('Follow') and mentions the batch limit, but fails to address idempotency (what happens if already following), side effects, or the content 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 description consists of a single, efficient sentence with zero redundancy. Every word serves a purpose: defining the action, the resource, and the critical operational constraint.

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 existing output schema, the description covers the essential constraint (max 50). However, the complete lack of schema descriptions means the description should have included parameter identification or format details to be fully complete.

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?

Given 0% schema description coverage, the description inadequately compensates for the undocumented parameter. While 'one or more' implies the array nature of 'artist_ids,' the description fails to specify the parameter name, expected format (Spotify URI vs. ID), or that the array is required.

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 resource ('artists'), and distinguishes from sibling tools like 'spotify_follow_users' by specifying the target entity. The inclusion of the 'max 50 per call' constraint adds necessary operational specificity.

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?

While the description includes the constraint 'max 50 per call,' it provides no explicit guidance on when to use this tool versus alternatives (e.g., 'spotify_check_following_artists' to verify first), nor does it mention prerequisites like authentication requirements.

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