在网易云客户端播放

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds a genuinely useful detail not in the annotations: the client is launched first if it isn't running. Beyond that it doesn't say whether the call blocks until playback starts, how errors from a missing client or unavailable track surface, or whether existing playback is interrupted.

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 sentences, front-loaded with the action and the resource types, followed by the client-launch side effect and the ID-source hint. There is no filler, and each clause carries information the agent needs.

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 two-parameter local-control tool with full schema coverage and annotations covering the safety profile, the description is close to sufficient, and the client-launch note closes the biggest behavioral gap. The remaining hole is the relationship to playback_control and any indication of failure/return behavior, which matters because there is no output schema to fall back on.

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%, with the type enum fully documented in the schema, so the baseline is 3. The description adds meaning on top: it ties the resource list to the type values and explains where ID values originate (search, get_* tools) and that they are numeric identifiers rather than names.

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 names a specific verb+resource in detail: it plays a song, playlist, album, artist's top songs, or radio on the local NetEase client, and it enumerates the exact five resource types. It can be told apart from the get_* / search siblings, though the closest sibling, playback_control, is not mentioned, which leaves a small ambiguity about which tool handles transport actions.

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 provides useful prerequisite guidance — IDs come from search or get_* tools — so an agent can chain discovery to playback. However, it never states when to use this tool versus playback_control, nor what happens on failure or with an invalid ID, so the when-to-use guidance is only implied.

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