comfyui_generate_image

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

Annotations already convey that this is not read-only, is not idempotent, and is open-world. The description adds the 'default txt2img workflow' context, but it does not disclose behavioral details like asynchronous queueing or blocking behavior, which are partially covered by the 'wait' parameter.

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 a single, concise sentence that is front-loaded with the verb and resource. Every word contributes meaning, with no fluff or repetition of schema details.

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 8 parameters and an output schema, the description is minimal but adequate for the core intent. It doesn't mention important behaviors like whether jobs are queued asynchronously or return immediately, which is a notable gap given the 'wait' parameter exists.

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 input schema documents all 8 parameters with clear descriptions (100% coverage), so the description does not need to elaborate. The phrase 'text prompt' reinforces the primary 'prompt' parameter, but adds no extra semantics beyond the schema.

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 states a specific action ('Generate an image') with a clear resource ('from a text prompt') and method ('using a default txt2img workflow'). It distinguishes itself from sibling tools like upscale or transform, though it doesn't explicitly contrast with comfyui_run_workflow.

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?

Usage is implied by the description: it is for generating an image from a text prompt. However, there is no explicit guidance on when to choose this over alternatives like comfyui_run_workflow or when not to use it, so the guidance is indirect.

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