move_items_between_playlists

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

Given no annotations, the description carries the behavioral burden, and it does well: it explicitly discloses that move removes from source, copy keeps source intact, dedupe skips existing target tracks, and dry_run previews without performing. It even details mode semantics. It doesn't mention possible partial failures, idempotency, or rate-limit considerations, so not a 5.

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 two tight sentences that front-load the core action and then clarify modes and options. Every clause earns its place with minimal redundancy.

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?

For a complex mutating operation with 8 parameters, the description covers the key decision points: copy vs move, dedupe, filter, and dry-run. It doesn't explain return values, but there is no output schema and the response_format parameter hints at what to expect. It could mention permission/ownership constraints or that it operates on Spotify playlist IDs, but overall it is reasonably 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 description coverage is 100%, so the schema already documents every parameter including mode, dedupe, filter, dry_run, max_results, response_format, and IDs. The description adds no extra parameter details beyond restating the mode and dedupe/filter concepts. Baseline 3 is appropriate.

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 states specific verb 'Bulk rehome items between playlists' and differentiates copy/move modes. It clearly identifies what the tool does. However, it doesn't explicitly distinguish itself from near-sibling 'move_tracks_between_playlists' and other playlist manipulation tools in the sibling list, so it loses a point.

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 explains when to use it via copy vs move semantics and mentions dedupe/filter options, giving implied usage context. But it does not explicitly state when to prefer this over alternatives like move_tracks_between_playlists, batch_add_to_playlist, playlist_union, etc., nor does it mention typical use cases or prerequisites like ownership/permission requirements.

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