suno_generate_song

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the tool 'Returns song IDs that can be used to check status,' which hints at an asynchronous process, but doesn't disclose critical details like whether this is a long-running operation, rate limits, authentication requirements, error conditions, or what happens to generated songs over time.

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 appropriately concise with two sentences that cover the core functionality and return value. It's front-loaded with the main purpose. However, the second sentence about checking status could be slightly more specific about the asynchronous nature of the operation.

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 generative tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the asynchronous workflow (how status checking works), doesn't mention typical latency or limitations, and provides minimal guidance on parameter usage despite the schema having good coverage of technical details.

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 description mentions 'custom lyrics and style' which aligns with the two required parameters, but adds no additional semantic context beyond what's already in the schema (which has 100% coverage). It doesn't explain relationships between parameters, provide examples of effective style tags, or clarify how lyrics structure tags affect generation quality.

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 purpose: 'Generate a song with custom lyrics and style.' It specifies the verb 'generate' and resource 'song' with key inputs. However, it doesn't explicitly differentiate from sibling tools like 'suno_generate_from_description' which likely serves a similar purpose with different inputs.

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 no guidance on when to use this tool versus alternatives. It mentions that returns can be used to check status, but doesn't explain when to choose this over 'suno_generate_from_description' or how it relates to other siblings like 'suno_check_status' and 'suno_download_song' in a workflow.

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