Rd Img2Img

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

With no annotations provided, the description must disclose behavioral traits. It does mention that inputs are resized to max side 512 and strength range 0-100, which is useful. However, it says nothing about output behavior, whether the operation is destructive to input files, return format, or side effects. The reference to 'same advanced options as rd_generate' is a pointer rather than a disclosure. Significant gaps remain.

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 concise with two sentences, but it is under-specified. It front-loads the core purpose and adds the resizing note, yet it relies on referencing another tool for advanced options. While it avoids verbosity, the brevity comes at the cost of essential information.

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 37 parameters, no annotations, and no output schema, this description is severely incomplete. It lacks information about expected outputs, error cases, how it interacts with other tools, and the meaning of most parameters. The agent would be unable to make an informed call without extensive further exploration.

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 by explaining the 37 parameters. It only clarifies the 'strength' parameter (0-100) and notes resizing, but it does not explain any other parameter such as prompt, seed, loras, model, etc. The vague 'same advanced options as rd_generate' does not provide semantic meaning for the current tool's parameters. This is a major deficiency.

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 identifies the tool as an image-to-image operation for refining/repainting existing PNGs, with a specific verb and resource. It also mentions the strength range and resizing behavior, which adds specificity. However, it does not explicitly differentiate from similar siblings like rd_api_img2img or rd_cn_img2img, though the name and 'Image to Image' label help.

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 implies usage on existing PNGs ('refine/repaint existing PNGs'), but it never explicitly states when to prefer this tool over rd_generate, rd_api_img2img, or other image-to-image variants. There are no exclusions or alternative conditions mentioned, leaving the agent to infer the intended use case.

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