delete-playlist

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

With no annotations provided, the description carries the full behavioral disclosure burden. It effectively discloses irreversibility ('Permanently delete'), a concrete cost ('Costs 50 quota units'), and a required safeguard ('Requires confirm: true'), which are useful non-obvious traits. It does not cover failure modes or permissions, but the key destructive aspects are well communicated.

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 a single, front-loaded sentence that conveys the core action, permanence, quota cost, and confirmation requirement without any filler. Every clause earns its place, making it highly concise and well-structured.

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 destructive operation with only two parameters, the description covers all critical aspects: what it does, the irreversible nature, the quota cost, and the confirmation guard. It does not describe the return value, but no output schema exists and return behavior is standard for delete operations. The information provided is sufficient for safe and correct invocation.

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 parameters are already well-documented in the schema. The description adds minimal extra meaning by restating the confirm requirement, but it does not introduce any new details about playlistId format or additional semantic constraints beyond what the schema provides.

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 'Permanently delete an entire playlist,' which identifies both the action (delete) and the target (playlist). This strongly distinguishes it from sibling tools like remove-from-playlist or clean-playlist that operate on individual items or partial contents.

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 when to use the tool—whenever you need to delete a whole playlist—but does not explicitly mention alternatives or conditions for not using it. Sibling tools like remove-from-playlist are not referenced, so the guidance is implicit rather than explicit.

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