playlist_remove

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

With no annotations present, the description carries the full safety burden and does disclose the critical trait: the operation is destructive and is gated behind confirm=true, with a dry-run preview as the fallback. It stops short of covering auth requirements, reversibility, or what happens when a listed track isn't in the playlist.

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 short sentences, zero waste, with the destructive warning and confirm requirement front-loaded in the second sentence. Every clause 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?

For a simple 2-required-parameter mutation tool with no output schema and no annotations, the definition covers the essential behavior an agent needs: what it does and the safety gate. Minor gaps remain around permissions and the behavior on non-matching items, but nothing blocking.

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 only 33% (only items is documented in the schema), so the description must compensate, and it does for confirm — explaining that omitting it yields a dry-run preview rather than a deletion. playlist_id remains undocumented but is self-evident; items' name/URI/URL flexibility is already handled by the 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?

States a specific verb and resource ("Remove songs from a playlist"), which is distinguishable from siblings like playlist_empty, playlist_delete, and unsave_tracks without opening the schema. It does not, however, explicitly contrast itself with those siblings, so it falls short of a 5.

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 implies the use case (removing individual songs from a playlist) but never states when to prefer this over playlist_empty (clear all) or playlist_delete. The confirm=true note gives operational context but is not routing guidance.

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