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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety. It adds valuable behavioral context: that listen_url is a preview link, not a release, and that it should only be shared when ready_to_share is true. It also instructs to include user_notice verbatim and to format remove_preview_url as a markdown link, which are specific behavioral requirements beyond the annotations.

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 concise and front-loaded with the core purpose and usage, followed by specific handling instructions. Each sentence earns its place; however, it could be slightly tighter by merging some clauses. It is not bloated and reads clearly.

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 read-only listing tool with annotations covering safety, the description is complete. It provides specific instructions on how to handle the returned data (sharing preview links, including user_notice, formatting remove_preview_url), which addresses the lack of an output schema. An agent has everything needed to correctly invoke the tool and use its results.

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 100%, so both parameters (limit and end_user_id) are already documented with their meanings. The description only implicitly references end_user_id ('for this end_user_id') without adding new details. The baseline of 3 is appropriate since the schema carries the parameter semantics, and the description does not enhance them further.

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 opens with a specific verb and resource ('List recent finished SoundBreak songs') and explicitly scopes it to 'this end_user_id'. It also states the intended use case ('Use when the user asks what songs they made'), which distinguishes it from sibling tools like get_song_generation_status (status) and remove_song_preview (removal).

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?

It gives a clear trigger context ('Use when the user asks what songs they made'), which is helpful for an agent to select this tool. It does not explicitly mention when NOT to use it or name alternatives, but the sibling list makes the distinction obvious. The instruction to share listen_url only when ready_to_share is true also guides conditional use.

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