spotify-mcp

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

Since annotations are absent, the description carries the full burden. It successfully discloses the batch limit ('max 50 per call'), which is critical behavioral context. However, it omits whether the operation is idempotent, error handling for invalid IDs, or that this requires user authentication.

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?

Extremely concise with zero waste—every word provides necessary information. However, the brevity is excessive given the complete lack of parameter documentation in the schema, forcing the agent to guess the parameter requirements.

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?

While an output schema exists (reducing the need to describe returns), the description is incomplete due to the undocumented parameter and lack of behavioral context (auth, idempotency) for a mutation operation. Given the 0% schema coverage, more detail was required.

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 for the required 'show_ids' parameter, the description fails to compensate by explaining what show IDs are, their format, or where to obtain them. The description does not mention parameters at all despite the schema providing no 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?

States the specific action ('Save') and resource ('shows'), and includes the important constraint 'max 50 per call'. However, it does not explicitly distinguish this from sibling save operations (e.g., spotify_save_albums) or clarify that 'shows' refers to podcasts.

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 no guidance on when to use this versus siblings like spotify_check_saved_shows, spotify_get_saved_shows, or spotify_save_episodes. No mention of prerequisites like authentication or valid show ID sources.

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