generate_image

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

With no annotations provided, the description takes on the full burden of behavioral disclosure. It thoroughly explains that the tool is non-blocking, takes 4-40 minutes, may cause timeout errors that are expected, and saves images to a configured output directory with embedded metadata. This is exemplary transparency.

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 well-structured and appropriately sized. It leads with purpose, then model options, then critical operational warnings. Every sentence contributes necessary usage or behavioral information, with no fluff or repetition.

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's complexity and lack of an output schema, the description covers the full lifecycle: what it does, which models to choose, how long it takes, what to expect regarding timeouts, and where results are saved. It even advises the user on how to handle the result. This is highly complete.

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?

All 7 parameters are fully documented in the input schema with defaults, ranges, and descriptions, so coverage is 100%. The description adds context about model-specific step defaults and performance differences, but this information is already largely present in the schema. Baseline 3 is appropriate since no significant additional semantics are provided.

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 it generates high-quality images using FLUX models, naming specific models (FLUX.1-dev and FLUX.2-dev). This specific verb+resource action distinguishes it from sibling tools like get_preview, unload_model, get_status, and set_timeout, which all have different purposes.

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 provides explicit guidance on how to handle the tool's long-running and non-blocking nature, including instructions to not treat timeouts as failures and to inform the user about background generation. It does not explicitly mention alternatives like get_preview for previews, but the usage context is clear and actionable.

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