netease_prepare_playlist_delete

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds critical behavioral details: the token is single-use and valid for two minutes, protected playlists are refused, and 'Preview is not user consent.' This prevents the agent from assuming the preview itself authorizes deletion.

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?

Three compact sentences front-load the core action and token outcome, then add prerequisites, exclusions, and the important consent caveat. No word is wasted.

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?

The description covers prerequisites, matching criteria, protected cases, token validity, and the non-consent warning. Since an output schema exists, describing the return shape is unnecessary, and the two required parameters are addressed sufficiently for 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?

With zero schema description coverage, the description carries the burden of explaining parameters. It maps id and expectedName to 'an exact owned playlist ID and name', adding meaning beyond the bare schema. It could be more explicit that expectedName must match the current playlist name exactly, but the existing wording is a meaningful improvement.

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 the tool's verb and resource: it previews deletion of an exact owned playlist by ID and name. It adds that it returns a single-use token, which distinguishes this preparation step from the sibling netease_delete_playlist that would actually perform deletion.

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 useful usage context: it requires NETEASE_ENABLE_PLAYLIST_DELETE=1, only works on exact owned playlists, and refuses collected, system, or configured protected playlists. It does not explicitly name an alternative such as netease_delete_playlist or state 'use this before deleting', but the preview-and-token flow makes the intended usage clear.

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