Rd Neural Transform

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the transformation intent and does not explain output behavior, nondeterminism, resource usage, file side effects, or failure modes. This is a material gap for a complex image-generation tool.

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 a single efficient sentence with no filler and front-loads the core purpose. However, the brevity comes at the cost of essential detail, so it is not ideal for a tool of this complexity.

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?

With 21 parameters, no annotations, no schema descriptions, and no output schema, the description is far too thin. It does not explain return behavior, parameter roles, typical usage, or effects on the input image, leaving an agent to guess on nearly every axis needed to invoke the tool correctly.

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%, and the description references only the input image and prompt concept. The other 19 parameters—seed, loras, model, steps, width, height, negative, adherence, cfg_scale, generations, return_image, and more—are left completely unexplained, so the agent cannot infer how to set them.

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 a clear operation: re-imagine an input image in a new style/pose from a prompt. This is specific enough to distinguish it from sibling tools like rd_neural_pixelate, rd_neural_resize, and rd_neural_detail, though it never names alternatives explicitly.

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?

There is no guidance on when to use this tool versus related tools such as rd_img2img, rd_cn_img2img, or rd_neural_detail. The single sentence implies a prompt-driven restyling use case, but gives no exclusions, prerequisites, or alternative-selection criteria.

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