flow_generate_image_with_references

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

With no annotations, the description carries the full burden, and it does add real constraints: per-model reference caps (10+4 vs 6+5+3), a 1-14 reference range, and 1-4 output images. It omits cost/latency implications, what happens when reference counts or types exceed the model limits, and whether generation is synchronous.

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?

Front-loaded with a one-line purpose, then model-specific limits, then a compact Args block that maps one line per parameter. Nothing is padded, though the model-limit lines consume space that could have been spent on reference-type rules or failure behavior.

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?

For a 9-parameter generation tool with no annotations and no output schema, the description covers inputs and model caps but leaves the return value (presumably file paths in output_dir) and error/limit behavior unexplained. An agent can call it, but cannot predict output shape or how over-limit references are handled.

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% across 9 parameters, so the Args block is doing essential work: it names the accepted model values ('fast', 'pro', 'lite', or a full id), bounds number_of_images to 1-4, and defers aspect_ratio/image_size/preset/style to flow_generate_image. Remaining gaps are the allowed aspect_ratio values, the meaning of preset vs style, and the expected path format for reference_image_paths and output_dir.

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 opening sentence gives a specific verb and resource ('Generate images') plus the distinguishing modifier ('guided by up to 14 reference images') with the reference types named. That differentiates it cleanly from flow_generate_image, whose behavior it explicitly inherits for shared parameters.

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?

Usage is only implied by the name and the reference-image framing; the description never states when to choose this over flow_generate_image (e.g. character consistency, style transfer) or when not to. It does reference flow_generate_image as the source of shared parameter behavior, which is a partial sibling link, but no explicit selection criteria are given.

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