读取网易云歌曲详情

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by listing the concrete output fields (name, artist, album, duration, official page link), which is especially useful because no output schema exists. It doesn't discuss error behavior or availability, but for a read-only metadata lookup this is adequate.

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, front-loaded with the input mode and output fields, with no filler or repetition. Every part carries meaningful information.

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?

This is a simple one-parameter read-only lookup with annotations and no output schema. The description covers the required input (song IDs) and the output fields, giving an agent enough to select and invoke it correctly. No critical missing context, such as destructive effects or authentication requirements, is relevant given readOnlyHint.

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%, so the description must clarify the parameter. It does: songIds are NetEase Cloud song IDs used to fetch details. Format and size limits are left to the schema pattern and maxItems, which is acceptable.

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 uses a specific verb ('读取' / read) and a precise resource: NetEase Cloud song details by song ID, enumerating the returned fields (name, artist, album, duration, official page link). This clearly separates it from siblings such as netease_lyrics (lyrics) and netease_search (search).

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 phrase '按网易云歌曲 ID' implies the tool is for when the agent already has song IDs and needs metadata. However, it does not explicitly say when to prefer this over netease_search or netease_lyrics, nor does it name alternatives or exclusions.

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