列出我创建的网易云歌单

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful auth and scope context ('使用本机登录会话', '当前账号拥有'), but it does not address failure modes such as missing login session or the exact return structure.

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?

One short sentence carries the action, scope, auth context, and downstream purpose. There is no filler or repetition of the name/title.

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 parameterless read-only list tool, the description gives essential context: auth session, account scope, and downstream purpose. The only missing piece is a precise description of the return structure, but '列出' makes a list of playlists the obvious result.

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?

The tool has zero parameters and schema description coverage is 100%, so the schema fully defines the input surface. No parameter elaboration is needed from the description.

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?

Description uses specific verb '列出' with clear resource '当前账号拥有的歌单', and the title further says '我创建的网易云歌单'. The phrase '供后续添加或移除歌曲' signals it is a listing/preparation tool, distinguishing it from modification/song-detail siblings.

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 explicitly frames the tool as a prerequisite for '后续添加或移除歌曲', giving a concrete when-to-use signal. It does not name alternatives or exclusions, but for this simple list operation the intended context is clear.

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