refine_image

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

No annotations provided, so description carries full burden. It discloses fetching source image, uploading to ComfyUI, and running denoising pass. It explains denoise effect but omits cost, time, failure modes, or file size limits. Adequate but not rich.

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?

Two concise sentences, front-loaded with key action and process. Every sentence adds value; no redundancy. Well-structured for quick parsing.

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?

No output schema, yet description does not mention what the tool returns (likely an image URL). Given 8 parameters and no output info, the description leaves significant gaps. Fails to provide complete context for agent 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 38% (only prompt, source_image_url, denoise described). Description adds context for denoise only. Other parameters (negative_prompt, steps, cfg, seed, checkpoint) remain unexplained. Partially compensates but insufficient.

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 'Refine an existing image using img2img' and explains the process. This distinguishes it from siblings like 'generate_image' (create from scratch) and 'generate_variations' (likely different img2img). Prompt+source inputs reinforce purpose.

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 explains when to use (to refine an existing image via img2img) and provides guidance on the denoise parameter ('lower denoise preserves...higher denoise gives more freedom'). However, it does not explicitly state when not to use or mention alternatives.

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