Rd Cn Txt2Img

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful behavioral context like preprocessing via 'process: bool', palette constraints via palette_files/palette_url, and 'Uses explicit steps (no quality)'. However, it does not disclose what the tool returns, whether images are saved, or any side effects.

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 compact and front-loaded with the core purpose. It packs useful parameter semantics into a small amount of text, though the dense semicolon-separated formatting is slightly hard to scan.

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?

This is a complex 37-parameter tool with no output schema and no annotations, but the description covers only a fraction of the parameters and no output or return behavior. It leaves many configuration semantics unexplained and does not clarify how multiple conditioning mechanisms interact.

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 gives meaningful semantics for the key required parameters 'controlnets' and 'control_images', including model enum values, weight range, and parallel PNG paths. However, 37 parameters exist and the vast majority (prompt, seed, loras, steps, width, height, light, negative, etc.) receive no explanation.

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 the tool performs 'ControlNet Text to Image', which clearly identifies the resource and operation: generating an image from text with ControlNet conditioning. It is clear enough to distinguish from img2img siblings like rd_cn_img2img, but it does not explicitly reference or differentiate against sibling tools.

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 provides no guidance on when to use this tool versus alternatives such as rd_api_txt2img, rd_cn_img2img, or rd_img2img. It explains some parameter mechanics but does not state prerequisites, exclusions, or the intended scenario for choosing this tool.

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