novelai_img2img

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions adjustable change strength (0.0 to 1.0) and optional noise, which gives some insight into behavior, but it does not disclose important behavioral traits such as whether the original image is modified in place, output file handling, or potential side effects. The description is not misleading but is incomplete for a mutation 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 concise, two sentences, and front-loads the core purpose. It mentions the key adjustable parameters (strength and noise) without excessive detail. However, it could be slightly more structured by explicitly listing the most important parameters or usage context, but it is appropriately sized for a tool description.

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?

Given the tool has 12 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the meaning of most parameters, the expected output format, or how the tool handles file paths and outputs. An agent would need to infer or guess the semantics of many parameters, making this insufficient for correct invocation.

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 for the 12 parameters. It explains the core concept of strength (change strength 0.0 to 1.0) and noise, but does not explain other key parameters like seed, size, model, scale, steps, sampler, output_dir, or negative_prompt. The description adds some meaning beyond the schema but leaves most parameters unexplained.

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 states the tool modifies or restyles an existing image using NovelAI Image-to-Image, with a specific verb ('Modify or restyle') and resource ('existing image'). It distinguishes itself from siblings like novelai_generate_image (which creates new images) and novelai_inpaint (which edits specific regions), making its purpose 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 implies usage for modifying/restyling existing images, which differentiates it from generation tools, but it does not explicitly state when to use this tool versus alternatives like novelai_inpaint or novelai_vibe_transfer. It mentions adjustable change strength and optional noise, giving some context, but lacks explicit when-to-use or when-not-to-use guidance.

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