cloud_music_artist_info

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or side effects. The description only states the action and one parameter, leaving the agent uninformed about operational characteristics.

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?

The description is very short (two lines), front-loaded with the purpose, and contains no fluff. The 'args:' line is slightly redundant but not harmful. Efficient for a simple tool.

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?

Given the tool's simplicity (one parameter, no output schema), the description minimally explains the outcome (artist details and top 10 songs). However, it lacks specifics about return structure, error handling, or usage context. Not fully complete but adequate for a basic retrieval tool.

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%, but the description adds meaning for the single parameter: 'artist_id: 歌手 ID' (artist ID). This clarifies the parameter's purpose beyond the schema's type-only definition. However, it lacks details like where to find the ID or any constraints.

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 explicitly states '获取歌手详情和热门歌曲 Top 10' (get artist details and top 10 popular songs), which is a specific verb+resource combination. It clearly distinguishes from siblings like album_info or search by focusing on artist details and top songs.

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?

No guidance on when to use this tool vs alternatives (e.g., search, album_info). No mention of prerequisites, context, or exclusions. The description only states what it does, not when to use it.

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