generate_music

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

Discloses model version (Music-2.6), output format (MP3 URL), cost (300 sats), and payment flow. However, does not specify if the operation is synchronous or asynchronous, potentially conflicting with the presence of check_job_status.

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?

Five sentences, front-loaded with key purpose, no redundant information. Efficiently conveys all critical details.

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?

Covers output and payment but omits details on job status polling or error handling, which may be needed given the complexity. The immediate 'Returns MP3 URL' statement may mislead if tool is actually asynchronous.

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 coverage is 100%, so description adds marginal value. It reinforces prompt structure (BPM, key, genre) and lyrics section tags, but does not significantly extend beyond schema descriptions.

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 'Generate full songs' with specific details like duration, AI vocals, and BPM/key control, distinguishing it from sibling tools like generate_image or generate_text.

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 explains payment requirements and prerequisite call to create_payment, and mentions parameters for customization. Lacks explicit when-not-to-use guidance but context with siblings is clear.

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