GPT Image 2 Official

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

With no annotations, description must disclose behavior. It explains that the startup preset owns provider/model/timeout/retry, and override rules for preset and api_key. Does not mention side effects, rate limits, or authentication details beyond api_key, but covers key behavioral points.

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?

Description is well-structured: purpose first, then override rules, then selection guidance, then prerequisite. It is not overly verbose but could be slightly more concise. Each sentence adds value.

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 complexity (16 params, 4 required, no schema descriptions), the description is incomplete. It omits explanations for most parameters and does not mention output/return values despite having an output schema. It does note a prerequisite (catalog call) but lacks depth.

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 description must compensate. It mentions some parameters (preset, api_key, image_size, aspect_ratio) but does not explain many others (version, mode, prompt, save_path, quality, etc.). The description adds limited meaning beyond what enum names imply.

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 'Generate or edit images via the OpenAI Images compatible gateway', specifying a verb ('generate or edit') and resource ('images'). It also hints at the distinction from siblings like gpt_image_2_temporary by referencing 'active startup preset', though not explicitly differentiating.

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?

Provides guidance on when to use (generation/editing) and prerequisites: 'Call list_image_tools_catalog first when you need the current supported size presets.' Also explains override behavior for preset and api_key. However, not explicitly states when not to use or alternatives.

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