spotify_cleanup_playlist

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

No annotations are provided, so the description must fully disclose behavior. It states that removal is optional and that a dry run is possible, but it does not clarify whether changes are permanent, what permissions are required, or how idempotent the operation is. The description only hints at destructiveness without details.

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 sentences, front-loading the purpose and adding a key usage hint. No extraneous information, though the hint could be integrated more naturally. It is efficiently concise.

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?

Although an output schema exists (so return values are covered), the description lacks context on what a dry run returns, how the tool handles errors, or any limitations (e.g., playlist size). For a potentially destructive tool, more operational context is needed.

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?

The input schema has 0% description coverage, meaning the parameter names and defaults provide all semantic information. The description only mentions the dry_run parameter and its default, but does not explain playlist_id, remove_unavailable, or remove_duplicates. This is insufficient for a 4-parameter tool.

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 that the tool finds and optionally removes unavailable and duplicate tracks from a playlist. It distinguishes itself from siblings like spotify_deduplicate_playlist (which likely only handles duplicates) by covering both unavailable and duplicate tracks.

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 mentions setting dry_run=False to apply, but does not specify when to use this tool versus alternatives like spotify_deduplicate_playlist or spotify_sort_playlist. There is no guidance on prerequisites, such as playlist ownership or edit permissions.

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