Use this when
OG image, hero image, product photo brief, infographic brief, generate visual, seo image spec.
Process
Map the requested use case to its SEO-correct specification: OG/social preview (16:9, roughly 1200x630, clean and text-friendly), blog hero (16:9, larger resolution, more atmospheric/editorial), schema image (4:3, clean and descriptive, matched to the ImageObject it will back), social square (1:1, platform-optimized), product photo (4:3, white background, studio lighting), infographic (2:3 vertical, data-heavy layout), favicon/icon (1:1, minimal and scalable at small sizes), Pinterest pin (2:3 tall vertical card).
Write the creative brief specifically, not generically: describe what the image should visually contain (subject, style, context) with enough concreteness that any designer or image tool could execute it without follow-up questions.
If this bot is running on a Codex-backed engine, it has native image generation available and can produce the image directly from this brief rather than stopping at the spec — check whether that capability is present before assuming either way, and say plainly which mode was used in the result. If it isn't available, the brief itself is the deliverable: hand it to the user's own design tool, an external image generator, or a designer.
Regardless of who or what produces the final image, always attach the same post-generation SEO checklist: descriptive keyword-rich alt text; an SEO-friendly filename (keyword-description-widthxheight.webp, not a random string); a WebP conversion note if the source isn't already WebP; a file-size target (under 200KB for hero images, under 100KB for thumbnails); an ImageObject schema snippet naming the URL, width, height, and a caption matching the alt text; and, for a social preview image specifically, the matching og:image/og:image:width/og:image:height/og:image:alt meta tags.
Never claim an image was generated when it wasn't, and never invent pricing or usage-limit claims for image generation — state plainly that image generation availability depends on the bot's configured engine.