generate_image

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention side effects, output format, or whether the tool blocks until completion. The 'wait' parameter exists in the schema but is not described in the tool description, leaving behavioral expectations vague.

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 front-loaded with a clear one-sentence purpose, followed by a necessary but lengthy JSON example. While the example adds length, it is directly relevant and earns its place. The structure is logical, with no wasted prose.

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 provides a complete workflow example and indicates the primary action, but it does not explain what happens after generation (e.g., where the image is saved, if it is returned) or any conditional behavior like the 'wait' parameter. Given no output schema and no annotations, this leaves gaps in the tool's overall context.

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 coverage is 100%, so the baseline is 3. The description adds significant value by including a detailed example workflow JSON, which clarifies the structure and expected format for the 'workflow' parameter. This goes beyond the schema's simple 'ComfyUI workflow JSON object' description.

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 function: 'Generate an image using ComfyUI with the provided workflow.' This is a specific verb+resource that distinguishes it from siblings like check_status and copy_image, which have entirely different purposes.

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 (generate an image when you have a workflow) but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. With siblings like check_status and copy_image, the intended use is clear by contrast, but no direct guidance is provided.

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