spotify-mcp

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

With no annotations provided, the description carries full burden. It discloses the write operation ('Save') and batch limit ('max 50'), but omits idempotency behavior, authentication requirements, and error handling (e.g., invalid IDs). The existence of an output schema reduces the need to describe return values.

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 sentence of 9 words with zero redundancy. The core action is front-loaded, and the parenthetical constraint '(max 50 per call)' is efficiently appended without disrupting flow.

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 tool with an output schema, the description meets minimum requirements by stating action, resource, and limit. However, with zero schema descriptions, it should ideally specify how to obtain valid episode_ids or reference related list/retrieve tools.

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 description coverage is 0%, so the description must compensate. It aligns the concept of 'podcast episodes' with the 'episode_ids' parameter, but does not specify ID format (Spotify IDs vs URIs), array structure, or data sources. Baseline compensation is partial.

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 uses specific verb 'Save' with resource 'podcast episodes' and distinguishes from siblings like spotify_save_tracks and spotify_save_shows by specifying 'podcast episodes' (individual installments vs. shows/subscriptions). The max 50 limit adds operational clarity.

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?

It provides the concrete constraint 'max 50 per call' which is critical for batching, but lacks explicit guidance on when to use this versus spotify_save_shows (for subscribing to full podcasts) or how to obtain episode_ids (e.g., from spotify_get_show_episodes).

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