Image Generation
Use Image Generation when the agent should create a brand-new visual during the conversation.
This tool is useful when the user wants an illustration, concept image, simple mockup, or another visual draft that does not already exist in your workspace.
When Image Generation Is the Right Tool
Use it when:
- The user asks the agent to create a new image
- The response should include a visual draft, not only text
- A generated concept is good enough for the next step, even if a human will review it later
Do not use it when:
- The answer should come from
Knowledge Baseor another existing source - You need an exact brand-approved asset that already exists
- The task needs a human designer to make precise final production artwork before anything is shared
Step 1: Add Image Generation
In Editor, open Tools, click Add Tool, and choose Image Generation.
Step 2: Choose an Image Model
Select the model the agent should use in Image Model.
Keep the first version simple. One model is enough to prove the workflow.
Step 3: Write a Narrow When to Use
Treat image generation as a deliberate behavior, not a default reply style.
Example:
Use this tool when the user asks for a new visual concept, illustration, or simple mockup that can be created from a text description. Do not use it for factual questions or when an existing approved asset should be reused.
That works because it defines:
- The kinds of requests that should trigger the tool
- The situations where the tool should stay off
- The difference between generating a new draft and reusing a real source asset
Step 4: Test with Prompts That Clearly Need an Image
Try prompts such as:
Can you create a hero image concept for a legal consultation landing page?Show me a simple illustration of the onboarding flow in a clean flat style.
Then confirm:
- The tool is actually called
- The returned image matches the requested direction
- The agent does not generate images for normal text-only questions
What the Agent Can Control at Runtime
The tool form only asks you to choose the model and define When to Use.
During the conversation, the agent can still decide image-specific details such as:
- The text prompt sent to the model
- Optional style direction
- Optional aspect ratio when the model supports it
Because of that, your invocation rule should explain what kinds of images the agent is allowed to create, not try to hardcode every visual detail in the tool setup.
Operator Tips
- Keep the trigger narrow so the agent does not generate images unless the user clearly wants one.
- If the image should follow a brand, campaign, or product style, describe that in
Instructionsor attach the relevant references. - If you want different visual behaviors, add separate
Image Generationtools and give each one a distinctWhen to Use. - Treat generated images as drafts unless your workflow includes a clear human review step.
Common Mistakes
Writing a vague trigger
Use this tool when visuals are helpful is too loose. The agent needs a real decision rule.
Using generation when a real source asset already exists
If the correct logo, diagram, or campaign image already exists, point the agent to that source instead of generating a new approximation.
Expecting the model choice to fix weak instructions
The model matters, but the agent still needs a clear request and good guidance about what kind of image is acceptable.