generate_image

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

With no annotations, the description carries full responsibility and excels: it reveals how reference image count changes behavior, states a hard limit of 6 images returning HTTP 400, explains that style follows the reference when 1 ref is used, and discloses the default save_path behavior and that the path is always reported. This is highly transparent.

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 information-dense and organized with clear sections, front-loaded with the core purpose before diving into details. It is somewhat long, but each sentence earns its place by conveying necessary behavioral nuance and parameter guidance. The structure follows a logical flow from purpose to reference-image rules to argument definitions.

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, lack of schema descriptions, and absent annotations, this description is remarkably complete. It covers usage, edge cases (3+ refs), error conditions (HTTP 400), return behavior ('returns the image itself' and path reporting), and parameter semantics. It leaves few gaps for an agent to misinterpret.

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 coverage is 0%, but the description meticulously explains every parameter: prompt ('full art-style description'), reference_images ('local file paths or public https URLs' plus the critical rule), size with examples ('1024x1024' or '1K'), ratio with examples, and save_path ('where to write the png' and default). It fully compensates for the sparse schema.

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 the tool's function: 'Generate an image from a text prompt.' It distinguishes itself from sibling tools like describe_image by specifying it generates rather than analyzes imagery, and the detailed behavior around reference images further clarifies its unique purpose.

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 gives explicit guidance on when to use 0, 1, or 3+ reference images, and explains the tradeoff between style and likeness control, including a practical workaround for both. It does not explicitly mention sibling alternatives, but the content strongly implies when this tool is appropriate for image generation tasks.

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