comfyui_transform_image

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

The description adds only the upload prerequisite, which is operational context rather than behavioral disclosure. It does not mention side effects, asynchronous behavior (despite the wait parameter), or what happens to the input image. Annotations already cover readOnly/destructive hints, so this minimal addition provides little extra transparency.

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 extremely concise—two sentences, front-loaded with the core purpose. Every word earns its place, and there is no redundancy or filler. This is an example of efficient writing.

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?

While the schema and annotations cover parameter semantics and safety, the description lacks broader context such as when to prefer this over comfyui_generate_image or comfyui_inpaint_image, or any workflow overview. The upload prerequisite is helpful but the description remains minimal for a tool with 8 parameters and an output schema.

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?

All 8 parameters have full schema descriptions (100% coverage), so the description is not required to elaborate on parameter meanings. The description itself adds no parameter-specific guidance, but the schema already handles this adequately, making 3 the appropriate baseline.

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 specifies a unique action: 'Transform an existing image using a text prompt (img2img).' This distinguishes it from sibling tools like comfyui_generate_image (likely txt2img) and comfyui_inpaint_image (region-specific editing). The verb+resource+method is specific and unambiguous.

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 explicitly states a prerequisite: 'The input image must already be uploaded to ComfyUI via comfyui_upload_image.' This gives clear context for when to use the tool. However, it does not name alternatives or explicitly exclude other tools, so it falls short of a 5.

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