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 of behavioral disclosure. It successfully conveys that range_length affects consecutive tracks and implies a write operation ('Move'), but fails to disclose error conditions (e.g., invalid indices), whether the operation is idempotent, or specific API constraints like rate limiting.

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 is a single, efficient sentence that front-loads the core action ('Move tracks within a playlist') and uses a parenthetical to clarify parameter semantics without redundancy. Every word serves a purpose.

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 is minimally adequate for a mutation tool with complex index manipulation. It lacks critical context for safe usage given zero input schema documentation—specifically index bounds checking, behavior when source and destination overlap, and confirmation that playlist_id refers to the target playlist being modified.

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 effectively compensates by explaining the relationship between range_start, insert_before, and range_length (consecutive). However, it omits details like 0-based indexing, valid ranges, or the default value behavior for range_length despite the schema showing a default.

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 moves tracks within a playlist and specifies the key positional parameters (range_start, insert_before), distinguishing it from sibling tools like spotify_sort_playlist (automatic sorting) and spotify_add_to_playlist (adding new tracks). However, it doesn't explicitly clarify the difference from spotify_update_playlist.

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 no explicit guidance on when to use this tool versus alternatives like spotify_sort_playlist, nor does it mention prerequisites such as playlist ownership requirements or valid index ranges. The parenthetical parameter explanation implies usage mechanics but not decision criteria.

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