Rd Cn Img2Img

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

With no annotations, the description carries the burden and does add useful behavior: the source image is appended after ControlNet slots and resized to 512, and strength is bounded 0-100. However, it says nothing about return values, output behavior, or side effects, so the disclosure is incomplete.

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 compact sentences front-load the purpose and state the exact differences with no filler. The parenthetical packs useful behavior without bloating the text.

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 tool is complex (39 parameters, 4 required, no output schema, no annotations), and the description only covers the delta from rd_cn_txt2img. An agent would still lack the shared parameter semantics, expected output, and invocation defaults needed to call it confidently.

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. It adds meaning for the delta parameters (source image, appended after ControlNet slots, strength 0-100) and references rd_cn_txt2img for the rest. Most of the 39 parameters still lack direct explanation, but the cross-reference and delta details provide partial coverage.

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?

Names the operation as "ControlNet Image to Image" and sharpens it by pointing to rd_cn_txt2img plus a source image and strength parameter. This directly distinguishes it from the most similar sibling.

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 makes clear this variant is appropriate when a source image should drive ControlNet generation, and implicitly points to rd_cn_txt2img when no source image is needed. It does not spell out exclusions versus other img2img or API siblings.

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