Generate image

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

With no annotations, the description carries the full behavioral burden but does disclose the key output contract: files are saved locally and their paths are returned. It says nothing about credentials/API key needs, latency, cost, rate limits, or failure modes, which are real concerns for a generation call against an external bot service.

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?

Three tight sentences: purpose first, then the editing case, then the output behavior. Every clause carries information an agent needs; no filler.

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 7-parameter tool with no output schema, the description covers the action, model selection, reference-image editing, and the return shape (saved paths). It could go further on auth requirements and on how `parameters`, `aspect_ratio`, and `prompt_flags` should be chosen between, though the schema's 100% coverage mitigates that.

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 100%, so the baseline is 3, but the description adds value beyond the schema: it names the default model (GPT-Image-1), lists concrete alternative bot names matching the `model` param, and clarifies that reference_images are for editing/remixing rather than just 'use as reference'.

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?

States a specific verb+resource ('Generate an image from a text prompt'), names the default model and several alternatives, and the local-save behavior. It is clearly distinguishable from generate_video, generate_speech, and generate_music.

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?

Gives usable selection guidance ('Pass reference_images to edit or remix existing pictures') and names the default bot when no model is supplied. It stops short of saying when to prefer this over the generic sibling generate_with_poe_bot, so there is no explicit alternative routing.

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