generate_music

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

With no annotations provided, the description carries the full burden. It discloses the output format (audio/video/cover URLs) and the special instrumental behavior. While it doesn't mention potential limitations or side effects, it covers the essential behavioral aspects for a generation tool.

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 a single, well-structured sentence that front-loads the main purpose and includes a critical usage tip. No redundant information; every word 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?

Despite no output schema, the description explicitly names the returned fields (audio URL, video URL, cover image), which is essential context. It also covers key parameter relationships. Minor gap: no mention of model version behavior or when to use vs. generate_lyrics, but overall adequate for the tool's complexity.

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 baseline is 3. The description adds value by linking prompt and make_instrumental (instrumental mode requires empty prompt), and clarifying the inspiration mode for gpt_description_prompt. This goes beyond the individual 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 custom music' and specifies return values (audio URL, video URL, cover image). This distinguishes it from the sibling tool generate_lyrics, which focuses on lyrics generation, making the purpose unambiguous.

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 provides clear usage context, especially for instrumental mode (leave prompt empty, set make_instrumental to true). However, it does not explicitly contrast with generate_lyrics or specify when to choose this tool over alternatives, so it lacks explicit exclusions.

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