generate_image

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

With no annotations, the description carries the full burden and does well: it discloses backend fallback ordering, the OPENAI_API_KEY prerequisite, rate-limit/unavailability triggers, and that results are written to disk. It doesn't cover what happens when both backends fail, or any cost/latency tradeoffs.

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 dense sentences, front-loaded with the action and output, followed by routing behavior and return shape. No filler; each sentence adds information.

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 multi-backend generation tool with no output schema, the description usefully states the return value ('file paths and the backend used') and the fallback behavior. The only gap is failure behavior when both backends are unavailable.

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 100%, so all seven parameters including enums and limits are already documented. The description only echoes the backend fallback already stated in the 'backend' field and adds no new parameter-level meaning.

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 and resource ('Generates a PNG image and saves it to disk') plus the multi-backend routing, so an agent knows exactly what the call produces. No sibling tools exist, so no differentiation is needed.

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 explains the default backend-selection logic (OpenAI first, ComfyUI on rate-limit/unavailability), which is useful context, but it never says when to call this tool versus not calling it, nor when an agent should override the 'auto' default.

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