netease_play_liked

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

Annotations already declare this is a non-read-only, non-destructive, open-world action, so safety is covered. The description usefully adds that it both builds a queue and starts playback, but it does not say whether the existing queue/playback is replaced or interrupted — meaningful behavior for a playback-control 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?

A single short sentence with no filler and the action front-loaded. It is efficient, though its brevity contributes to the missing parameter and behavior detail.

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 playback action with zero schema documentation, an undocumented mode enum, and no output schema, the description leaves too much unsaid — particularly what mode does and how existing playback is affected.

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%, and the description mentions no parameters at all. The mode enum (sequence/shuffle/repeat_one) is never referenced, so the agent must inspect the schema to learn that playback ordering is even configurable, and requestId remains unexplained.

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 pair: build a queue from 'my liked music' and start playback. That distinguishes it from netease_liked_songs (listing) and netease_play_playlist (arbitrary playlist), though it never names those siblings explicitly.

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?

There is no statement of when to use this versus netease_play, netease_play_playlist, netease_play_daily, or netease_liked_songs. Usage can only be inferred from the verb itself; no conditions or exclusions are given.

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