spotify-mcp

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

With no annotations provided, the description carries the full disclosure burden. It successfully communicates the batch size limit (50 URIs), but fails to disclose idempotency behavior (are duplicates handled?), authentication requirements, or side effects of the write operation.

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 structure is perfectly front-loaded with the action and destination, and efficiently incorporates the critical limit constraint without any extraneous text. 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?

Given that an output schema exists, the description appropriately omits return value details. However, for a write operation with no safety annotations, the description should disclose error handling or destructive potential to be complete enough for safe agentic use.

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?

The schema has 0% description coverage (only title 'Uris' provided). While the description mentions 'URIs' confirming the expected content type, it fails to compensate by explaining the URI format (e.g., 'spotify:track:xxx'), validation rules, or providing examples that the schema omits.

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 ('Save tracks'), the destination ('your Liked Songs'), and distinguishes from siblings like 'spotify_add_to_playlist' (which targets specific playlists) and 'spotify_get_saved_tracks' (which retrieves rather than writes).

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 operational constraint 'max 50 URIs per call,' which is essential for correct invocation. However, it lacks explicit guidance on when to use this versus 'spotify_add_to_playlist' or how it relates to the user's library management workflow.

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