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

Annotations already indicate read-only and non-destructive behavior. The description adds meaningful operational details: only finished songs are returned, listen_url should only be shared when ready_to_share is true, links are previews not releases, user_notice must be included verbatim, and remove_preview_url should be rendered as a 'Remove preview' markdown link.

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 three tight sentences with no filler. The first sentence states the core action, the second gives the trigger context, and the third delivers the key operational constraints. It is front-loaded and every sentence earns its place.

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 read-only list tool with full schema coverage and safety annotations, the description covers usage trigger, parameter emphasis, and important output-handling rules despite the absence of an output schema. Nothing critical is missing for an agent to invoke and use this tool correctly.

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 limit and end_user_id are already fully documented in the schema. The description's reference to 'this end_user_id' reinforces a parameter but does not add meaning beyond the schema, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'List recent finished SoundBreak songs for this end_user_id.' It also names the exact user trigger ('Use when the user asks what songs they made') and is distinguishable from siblings like list_artists and get_song_generation_status.

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 description explicitly provides the when-to-use signal: 'Use when the user asks what songs they made.' It does not explicitly contrast alternatives such as get_song_generation_status for unfinished songs, but the context is clear enough for a read-only list operation.

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