generate_music

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

No annotations are provided, so the description must carry behavioral disclosure. It discloses polling behavior and download path ('Polls until done and downloads to kie/assets/raw/'), which adds value. However, it does not mention authorization needs, rate limits, or potential costs (e.g., credit usage), leaving gaps 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 three concise sentences with clear front-loading. The first sentence states the core purpose, the second lists supported models and duration, and the third gives use cases and behavior. No superfluous words.

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?

No output schema exists, so the description should cover return values. It mentions polling and download path but does not describe what the tool returns (e.g., a result object, task_id for async, or downloaded file path). Given the tool's complexity (9 params, generation), this omission is notable.

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 baseline is 3. The description does not add significant meaning beyond the schema; it only restates model versions and duration. The schema already provides detailed parameter descriptions, so no additional value is needed.

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 generates music using Suno via kie.ai, lists supported models (V5.5, V5, V4.5+, V4.5, V4) and duration (up to 8 minutes), and specifies use cases (game music stems, ambient tracks, jingles). This verb+resource combination effectively distinguishes it from sibling tools like generate_sfx or generate_video.

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 implies usage for game music, ambient, and jingles but provides no explicit guidance on when to use this tool vs alternatives (e.g., generate_sfx for sound effects, generate_gemini_tts for speech). No when-not-to-use or alternative mentions are present.

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