spotify-mcp

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

No annotations provided, so description carries full disclosure burden. Adds valuable operational constraint 'max 50 per call' indicating API limits. Missing: read-only safety confirmation (though implied), error behavior for exceeding limit, and whether results preserve input order.

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 efficient sentence (11 words) with zero redundancy. Critical constraint (max 50) included without verbosity. Every word earns its place.

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?

Adequate for a simple validation tool with existing output schema. Captures the essential batch limit. Minor gap: could explicitly state that show IDs must be provided to check, given the parameter lacks schema 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 has 0% description coverage for the 'show_ids' parameter. Description implies input is required via 'Check which shows' but fails to explain parameter format, that it accepts an array, or ID syntax expectations. Insufficient compensation for zero schema documentation.

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 specific verb ('Check') + resource ('shows') + scope ('in your library'). Effectively distinguishes from sibling 'spotify_get_saved_shows' (which retrieves all saved shows) by implying a validation operation against specific inputs.

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?

Provides the concrete constraint 'max 50 per call' which signals batching requirements. However, lacks explicit guidance on when to use this versus 'spotify_get_saved_shows' or how to handle pagination if checking more than 50 shows.

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