netease_delete_playlist

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

The description adds substantial behavioral detail beyond the annotations: the token is consumed once, the operation rechecks account and playlist attributes, verifies removal and preservation of other playlists, never auto-retries, and backups cannot restore original IDs or followers. This is excellent disclosure for a destructive, non-idempotent tool.

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 dense and well-structured: precondition first, then the core action, then verification and safety constraints. Every sentence adds meaningful information without fluff.

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 single-use operation, the description covers authorization, token consumption, verification, non-retry behavior, and irreversibility caveats. An output schema exists, so return value documentation is not required. The only minor implicit detail is the source of the token, but the sibling list makes that clear enough.

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 description coverage is 0%, but the description compensates by explaining that the token is a deletion preview token, tied to ownership and single-use consumption. It does not explicitly state where the token comes from or its expiry, but the uuid format and pattern in the schema cover the validation aspects.

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 a specific action: consume a deletion preview token and delete an owned playlist once. It distinguishes this from siblings by emphasizing it is the final deletion step, not preparation, listing, or status checking.

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 clear usage context: use only after explicit user authorization and with a deletion preview token. It also forbids automatic retries on uncertain results. It does not explicitly name the prerequisite sibling prepare_playlist_delete, but the token language strongly implies the required flow.

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