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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the polling loop semantics, the condition for sharing the listen_url, and the limitation of no in-chat widget. No contradiction with 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?

Three sentences with zero waste. Purpose is front-loaded, followed by usage instructions and a limitation. 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 polling status tool, it explains the entire call loop, the conditions to act on the result, and a limitation. Though no output schema, it implies response fields (poll_again, generation_status, ready_to_share, listen_url) sufficiently for an agent to use 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 parameters are already documented. The description only reiterates using the same end_user_id and linking to create_song_generation, which adds minimal value beyond the schema. Baseline 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?

States specific verb 'Poll' and resource 'song generation', clearly distinguishing it from sibling tools like create_song_generation, list_my_songs, or remove_song_preview. An agent can immediately identify its role without ambiguity.

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?

Explicitly instructs to call after create_song_generation, pass the same end_user_id, keep polling while poll_again is true, and share listen_url only when generation_status is complete and ready_to_share is true. Gives precise sequencing and conditional behavior.

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