unpin_playlist

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

There are no annotations, so the description carries the behavioral burden. It openly reveals the mutation via 'DELETE /playlists/{id}/followers' and notes dry_run support, which is useful. However, it does not disclose side effects, permission requirements, reversibility by re-pinning, or what happens on success/failure, leaving meaningful gaps.

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 no fluff; the core action and endpoint are front-loaded. The phrase 'elicitation for bulk use' is jargon-heavy and could be clearer, but overall the description is compact and scannable.

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 unfollow operation with a fully documented schema, the description is mostly sufficient to select and invoke the tool. But with no annotations and no output schema, it omits return behavior, authorization needs, and clarification of 'elicitation.' The endpoint reference partially compensates, but an agent still lacks some operational context.

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 100%, so the structured descriptions already document playlist_id, dry_run, and response_format. The description's mention of dry_run adds little beyond the schema, and 'elicitation' is mentioned without explanation. It provides only slight context that dry_run is intended for bulk use.

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 opens with a specific verb and resource: 'Unfollow (unpin) a playlist.' It also includes the underlying API endpoint, which removes any ambiguity about what operation is performed. This clearly distinguishes it from related tools like pin_playlist, unfollow_artists, or remove_from_library.

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 explicit guidance on when to use this tool versus alternatives. 'Supports dry_run and elicitation for bulk use' hints at bulk scenarios but does not define them or cite sibling tools. An agent must infer that this is the right tool for unfollowing playlists from the name and action phrase alone.

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