netease_play_hot_chart

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

The annotations already disclose a non-read-only, non-destructive, open-world playback action. The description adds chart-specific targeting but does not explain important side effects such as whether it interrupts current playback, replaces the queue, or requires account/login state.

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 with no filler. Every clause earns its place by stating the target chart and the no-substitution constraint.

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 playback command with annotations present, the description covers what the tool does but leaves the required requestId unexplained and gives no guidance on how mode affects playback. It is minimally usable but not fully complete.

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%, yet the description says nothing about the required requestId or the mode enum values. The mode labels are somewhat intuitive, but the description does not compensate for the missing parameter documentation.

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 gives a specific verb and resource: identify and play the NetEase Cloud hot song chart. It also explicitly excludes substituting other charts, which distinguishes it from siblings like netease_play_playlist and netease_play_daily.

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?

Usage is clear for requests targeting the hot chart, and '不替换为其他榜单' adds an explicit negative constraint against falling back to another chart. However, it does not name alternative sibling tools or state when those should be preferred.

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