suno_generate_lyrics

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

No annotations are provided, so the description carries the full burden. It discloses that the output includes section markers like [Verse] and returns title, status, and formatted text. It does not mention destructive behavior, rate limits, or authentication needs, but for a generation tool, these are less critical. The model parameter behavior could be explained more, but overall it is adequate.

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 well-structured: a clear purpose sentence, bulleted usage conditions, and a note about output format. It is concise without being overly terse, though some sentences could be combined without losing clarity.

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?

The description covers the tool's purpose, usage guidelines, output format, and integration with another tool. Given the presence of a detailed input schema and the implied output schema, the description is complete enough for an AI agent to understand when and how to use the tool.

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?

Both parameters have detailed descriptions in the input schema (100% coverage). The description adds context about the output format but does not significantly enhance parameter understanding beyond what the schema already provides. Baseline score of 3 is appropriate.

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 it generates song lyrics from a text prompt and creates structured lyrics with proper song sections (Verse, Chorus, Bridge). This distinguishes it from sibling tools like suno_generate_music or suno_generate_custom_music, which focus on audio generation.

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 lists specific use cases such as needing lyrics without writing them or requiring structured lyrics with section markers. It also mentions the output can be used with suno_generate_custom_music. However, it does not explicitly state when not to use this tool or provide alternative tools for different scenarios.

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