generate_image

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

With no annotations present, the description carries the full behavioral burden, and it delivers: it reveals the execution path (ComfyUI run-template, same run path as run_workflow), the local-vs-remote behavior via COMFYUI_URL/COMFYUI_HOST and 'never Cloud', the cost model ('Always FREE'), the synchronous/asynchronous behavior of wait, and the effect of timeout_seconds. It even notes checkpoint must be pre-installed on the machine that runs the job.

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-line purpose, then uses compact labeled sections (Args, Returns, Gotchas). Every sentence carries information — environment variables, parameter effects, routing guidance, and return shape — without fluff or repetition.

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 no output schema and no annotations, the description covers everything needed to invoke it correctly: the return envelope (prompt_id + outputs), the alternative routing to sibling tools, the model prerequisite, sync/async semantics, and environment overrides. No meaningful gap remains for correct usage.

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 for the bare schema. It does: the Args section gives the meaning and interaction of checkpoint, wait, and timeout_seconds, including how wait changes timeout behavior and how to poll with job(action='status'). This fully bridges the schema gap.

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?

Opens with a specific verb and resource ('Generate an image from a text prompt') and immediately brands itself as 'the fast on-ramp.' It distinguishes itself from siblings by naming run_workflow and partner_generate and stating it runs ComfyUI's default SD1.5 template, so an agent can tell exactly what it does and what it is not.

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?

Explicitly tells the agent when to use this tool versus alternatives: use partner_generate for paid PARTNER models, and use search_templates -> fetch_template -> run_workflow for chosen templates or hand-authored workflows. It also explains the wait=True/False behavior so the agent can choose between synchronous and polling-based consumption.

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