generate_lyrics

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

The description mentions the tool returns a task id, status, and output URLs, but omits key behavioral traits: it is an async operation, waits can be configured via the 'wait' parameter, and it may require polling. No annotations exist to supplement.

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 very short (one sentence), which is concise but at the cost of essential information. It could be restructured to include key behavioral facts without being verbose.

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?

With 5 parameters, no output schema, and no annotations, the description fails to cover the tool's complexity. It does not explain the async nature, required inputs, or polling behavior, making it inadequate for agent invocation.

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?

Out of 5 parameters, only 'wait' has a description in the schema. The tool description provides no additional meaning for any parameter, leaving prompt, callback_url, timeout_ms, and poll_interval_ms entirely unexplained.

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 creates a Suno task for generating lyrics, which distinguishes it from sibling tools like text_to_music or text_to_sound. The verb 'create' and resource 'Suno task' are specific.

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?

No guidance on when to use this tool versus alternatives. No prerequisites or context provided, such as requiring a valid API key or that the task is asynchronous.

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