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. It discloses the optional nature of removal and the dry_run safety mechanism, but lacks details on what the output contains (though an output schema exists), rate limits, or whether removed tracks are recoverable.

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 description consists of two efficient sentences. The first establishes core functionality; the second provides the essential safety instruction regarding dry_run. No words are wasted.

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 presence of an output schema (covering return values) and the description's coverage of the safety-critical dry_run parameter, the description is sufficiently complete for a 4-parameter tool. It adequately explains the dual-mode behavior (detection vs. deletion).

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 successfully maps 'unavailable' and 'duplicate' to their respective boolean parameters, and explicitly explains the dry_run logic ('Set dry_run=False to apply'). The playlist_id parameter is implied by context.

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 tool finds and optionally removes both unavailable and duplicate tracks, distinguishing it from the sibling 'spotify_deduplicate_playlist' which likely handles only duplicates. It uses specific verbs ('Find', 'remove') and identifies the resource (playlist tracks).

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 description provides critical usage guidance by explicitly stating 'Set dry_run=False to apply,' which is essential since the schema shows dry_run defaults to true. This prevents accidental modifications. However, it doesn't explicitly state when to use this versus 'spotify_deduplicate_playlist' or other alternatives.

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