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 and successfully discloses the 100-item limit and default append behavior vs. optional position insertion. However, it lacks details on error handling, duplicate track behavior, or idempotency guarantees.

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?

Two efficient sentences with zero waste. Critical constraint (max 100) appears early, followed by positioning behavior. 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 the output schema exists, the description appropriately omits return value details. However, with 0% schema coverage across 3 parameters, the description should ideally document parameter formats or validation rules to be 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?

Schema coverage is 0%, requiring the description to compensate. It implies 'track URIs' for the uris parameter and mentions 'position', but provides no format guidance for playlist_id or URI structure (e.g., spotify:track:xxx). Baseline compensation for undocumented schema.

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?

Description clearly states the specific action (Add track URIs), target resource (playlist), and key constraint (max 100 per call). The verb-resource combination distinguishes it from siblings like spotify_create_playlist (creates empty playlist) and spotify_update_playlist (modifies metadata).

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?

The 'max 100 per call' constraint implies batching requirements, but there is no explicit guidance on when to use this vs. spotify_create_playlist or spotify_add_to_queue. No mention of prerequisites like playlist ownership or URI format requirements.

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