Delete Playlist

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

Annotations already declare destructiveHint=true and readOnly=false, and the description goes beyond them by adding permanence, the confirmation requirement, the prerequisite of prior display, and the key side effect that songs are not deleted. This materially improves safe invocation.

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 compact English sentences front-load the action and risk, followed by a concise Chinese restatement. Every sentence carries safety, scope, or side-effect information with no filler.

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 destructive tool with no output schema, the description covers prerequisites, side effects, parameter constraints, and prohibited use cases. An agent has enough information to call it correctly and avoid data loss.

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 baseline is 3; the description adds value by constraining playlist values to tool-created demo/temporary playlists and emphasizing that confirm must be explicitly true. This is a meaningful extension beyond the schema, though not exhaustive.

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 object ('Delete one playlist permanently') and immediately clarifies scope: it does not delete underlying songs and only targets tool-created demo/temporary playlists. This clearly differentiates it from inspection, creation, and audit siblings.

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?

It states exactly when the tool may be used—only after the playlist has been shown to the user and explicitly confirmed—and when it must not be used, namely on user-curated playlists. The confirm=true requirement acts as an actionable gate for the agent.

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