netease_play_daily

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds the account-specific daily-recommendation context but does not disclose playback side effects such as whether it replaces the queue, requires an active device, or needs authentication.

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 front-loaded sentence with no wasted words. It is efficient, though extremely terse given the tool has multiple parameters and playback behavior to explain.

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 tool with 0% schema description coverage and no output schema, the description is too sparse. It conveys the core action but leaves mode semantics, requestId purpose, authentication needs, and playback side effects undocumented.

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 does not mention either parameter. It gives no meaning for the required requestId or for the mode enum values (sequence, shuffle, repeat_one).

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 states a specific verb (播放) and resource (今天的每日推荐歌曲), clearly identifying the daily-recommendation playback action. It is distinguishable from siblings like netease_play_liked or netease_play_playlist, though it does not explicitly name alternatives.

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 implied by the phrase '账号今天的每日推荐歌曲' — use it when you want to start playback of today's personalized recommendations. There is no explicit when-not guidance or comparison to sibling playback tools.

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