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 successfully discloses the safe-by-default behavior (dry_run defaults to true), but omits what constitutes a 'duplicate' (track ID match vs. metadata), whether removal is reversible, or specific auth/permission requirements.

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 sentences with zero redundancy: the first establishes purpose, the second provides the essential safety instruction. Every word earns its place in a highly front-loaded structure.

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 the output schema handles return values, the description leaves a gap regarding deduplication logic (e.g., exact matches vs. acoustic duplicates). It meets minimum viability for a destructive operation tool but could enhance confidence by defining match criteria.

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?

Given 0% schema description coverage, the description compensates effectively by explaining the critical dry_run parameter semantics (False = actual removal). While playlist_id lacks explicit description, its purpose is inferable from the tool name, making this adequate compensation for the schema gap.

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 ('Find and optionally remove duplicate tracks') and target resource ('playlist'), using precise verbs that distinguish it from general 'cleanup' or 'update' sibling tools.

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 explicit instruction on how to execute removal ('Set dry_run=False to remove'), effectively explaining the safety mechanism. However, it lacks guidance on when to choose this over alternatives like 'spotify_cleanup_playlist' or prerequisites for the playlist_id format.

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