generate_image

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

No annotations are provided, so the description carries full burden. It explains generation behavior (resizing/cropping to nearest valid size, multiple variants using seeds, saving to output_path, return format). It does not mention overwrite behavior, auth requirements, or computational cost, but covers essential behavioral traits.

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 compact and well-structured: a lead sentence defining the action, followed by concise bullet-like explanations for key parameters (size, n, seeds, returns). Every sentence adds value, no redundancy.

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 no output schema, the description includes return format. It covers size flexibility, multi-image generation, and output saving. However, it lacks details on step parameter semantics, negative prompt effects, and potential edge cases (e.g., path conflicts). Still, it is largely complete for an AI agent.

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%, so description compensates by explaining size (named presets or width+height), n and seed inference, and the return object. It does not detail steps or negative prompt semantics, but most parameters are covered sufficiently for usage.

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 explicitly states 'Generate web-dev image(s) with Z-Image Turbo and save to output_path', clearly identifying the verb (generate), resource (web-dev images), and output. Sibling tools (health, list_presets) are completely unrelated, so no confusion.

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 does not provide explicit when/when-not guidance, but the purpose is distinct from siblings, and the parameter explanations implicitly define usage context. It would benefit from stating 'Use this to generate images, not for health checks or listing presets'.

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