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

With no annotations provided, the description carries the full burden and does well: it discloses the cost (500 sats per song), payment method (Bitcoin Lightning), return format (MP3 URL), and model capabilities. It lacks details on potential asynchronous behavior or failure modes, but the key operational traits are covered.

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 efficiently front-loaded with the core function, then provides additional context on model, usage, pricing, and payment. Every sentence contributes unique information with no redundancy or fluff, making it well-structured despite its length.

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?

Given the complexity (9 params, no output schema), the description covers essential aspects: purpose, usage guidance, cost, payment flow, and output format. It does not explain error handling or whether the call is synchronous vs. async, but the sibling tools (await_result, check_job_status) partially mitigate that gap.

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 schema has 100% coverage with detailed parameter descriptions, so the baseline is 3. The description adds a useful hint for the prompt parameter ('Specify BPM, key, genre, mood in prompt') and references section tags, but it does not go beyond what the schema already provides for other parameters.

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's function: 'Generate full songs (up to 6 min) with natural AI vocals, BPM/key control' and specifies the output as an MP3 URL. It distinguishes itself from sibling tools like generate_image, generate_text, and generate_video by focusing on music generation with unique capabilities like section tags and Music-2.6 model.

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?

Provides clear context on how to use the tool: 'Specify BPM, key, genre, mood in prompt' and mentions the payment prerequisite ('Requires create_payment with toolName="generate_music"'). However, it does not explicitly name alternatives or when not to use this tool, so it does not fully meet the 'explicit alternatives' criterion.

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