comfyui_generate_audio

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds useful behavior ('Empty arguments keep the workflow's own values', `extra` overrides, `workflow` swaps presets), but does not disclose async behavior, the meaning of `wait`/`timeout`, or what the call returns, which are significant 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 compact, front-loaded with the primary purpose, and every sentence provides actionable information. It avoids redundancy and presents the most important usage semantics in a scannable format.

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 tool with 10 parameters, no annotations, and no output schema, the description covers the core generation workflow but leaves important operational details unstated, such as how results are returned, how `wait`/`timeout` behave, and what `negative_prompt` does. It is adequate for basic use but has clear gaps for reliable 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?

Schema description coverage is 0%, so the description must compensate. It explains five parameters (`prompt`, `lyrics`, `duration`, `extra`, `workflow`) clearly, but omits `seed`, `steps`, `negative_prompt`, `wait`, and `timeout`, leaving half the parameters semantically unclear despite the 'empty arguments' hint.

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 a specific action ('Generate audio/music') and the resource ('default audio workflow'), which distinguishes it from sibling image, video, and asset generation tools. Backticked parameter names reinforce the core function without ambiguity.

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 makes the intended use context clear: audio/music generation via the preset 'audio' workflow. It explains how to customize prompt, lyrics, duration, and workflow, but does not explicitly contrast with generic alternatives like comfyui_run or other generation tools, so exclusions are left to inference.

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