歌曲详情

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the concrete fields returned (name, artist, album, duration, VIP flag), which matters because there is no output schema. It stops short of covering partial-failure or invalid-ID behavior.

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 front-loaded sentence that names the keying input first, then the returned fields. No filler and nothing redundant with the 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 one-parameter lookup with no output schema, the description carries the important missing piece by listing what comes back per song. Only edge-case behavior (unknown or unavailable IDs, VIP-restricted tracks) is left unstated.

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 coverage is 100% and the single parameter documents type, bounds and the 200-item cap. The description's '根据歌曲 ID 批量获取' only reinforces the array/batch nature already stated in the schema, adding no new syntax or constraint detail.

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?

States a specific verb (批量获取) and resource (歌曲信息) scoped by song ID, and enumerates the returned fields (歌名、歌手、专辑、时长、是否 VIP). An agent can distinguish it from search, get_lyrics or get_similar_songs by the ID-keyed lookup, though no sibling is named 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?

Usage is implied: call it when you already hold song IDs, in batches. There is no explicit when/when-not guidance, e.g. that IDs typically come from search or a playlist listing, and no note on what to do for unknown IDs.

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