playlist_exclude_artists

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

With no annotations, the description carries the disclosure burden. It does reveal the operational pattern ('Quota: GET + chunked deletes') and states the destructive verb 'Remove', which is useful. However, it never warns about permanence/irreversibility, undo options, or the safety default of dry_run, leaning on the schema instead.

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 with the main action front-loaded and the quota note earning its place as operational context. No filler, no restated schema content.

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 mutating tool with no annotations and no output schema, the description could do more: it doesn't address the destructive consequences, preview safety path, or relation to the many playlist-mutation siblings. The rich schema covers parameters but the behavioral/service-level context is thin.

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?

Shcema description coverage is 100%, and every parameter (dry_run, artist_ids, playlist_id, dedupe_scope, response_format) is already well-documented with defaults and enums, the description adds no parameter meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 uses a specific verb ('Remove'), names the resource ('every track by one or more artist IDs from a playlist'), and adds the memorable 'purge the artist one-shot' framing that signals bulk, all-at-once behavior. It's distinguishable from read-only siblings, though it doesn'it explicitly compare against the very similar playlist_remove_artist tool.

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 gives no when-to-use vs alternatives guidance. Given near-twin siblings like playlist_remove_artist, filter_playlist_by_artist, and dedupe_playlist_apply, an agent has no criteria for choosing this one. The quota hint hints at cost but not selection logic.

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