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

Reveals important non-obvious behaviors beyond annotations: generation is asynchronous and requires polling, song count depends on account state (complimentary=1, connected=2), there is no in-chat widget, and end_user_id must stay stable and not be invented. No contradiction with readOnlyHint=false.

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?

Purpose is front-loaded and every sentence carries an operational fact. It is slightly longer than necessary and repeats some end_user_id guidance already present in the schema, so it is not a perfect 5.

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?

Even without an output schema, the description closes the execution loop: after the call, poll with generation_id and the same end_user_id until complete, then share listen_url. Combined with the detailed schema, an agent has enough to invoke the tool and follow up 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?

The input schema already covers all 7 parameters with descriptions, so the baseline is 3. The description adds cross-parameter meaning: reuse end_user_id on polling, prefer artist_name over ai_cowriter_id, and interpret song_count via account state. This adds real value beyond the schema.

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?

Opens with a specific verb ('Start') and a specific resource ('SoundBreak song generation'), with the AI-artist scope attached. This is immediately distinguishable from the read-only/list/status/removal siblings, so an agent knows this is the creation entry point.

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?

Gives explicit operational guidance: pass the same end_user_id, prefer artist_name, poll get_song_generation_status after this returns, and share listen_url because there is no widget. It stops short of explicitly naming when-not situations or alternative tools, but the sequencing and conditions are clear.

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