cloud_music_play

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

The description mentions invoking a client (唤起客户端) which implies an external action, but does not disclose side effects, required client state, or what happens on failure. No annotations to fill gaps, so description carries full burden but is insufficient.

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 extremely concise: one sentence for purpose, then clear parameter explanations. Every part is useful with no redundancy. Front-loaded with the main action.

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 simple 2-parameter tool with no output schema, the description covers the basic function and parameters. However, it lacks info on return values, error handling, and client dependencies, leaving some gaps for an agent.

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?

With 0% schema description coverage, the description adds meaning: id is explained as '歌曲ID 或 歌单ID' and type as 'song' or 'playlist'. This clarifies the parameters beyond the raw schema types, though format details are missing.

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 clearly states the tool plays a specified song or playlist (唤起客户端播放指定歌曲或歌单), distinguishing it from siblings like cloud_music_add_to_playlist or cloud_music_status. The verb 'play' and resource 'song/playlist' are specific.

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., when to choose this over cloud_music_my_playlists or cloud_music_status. No exclusions or prerequisites mentioned.

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