generate_image

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

Discloses saving locally and returning absolute paths, but no annotations are provided to cover safety, destructive intent, or rate limits. The description carries the full burden but omits details like potential overwriting, API usage costs, or required authentication.

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?

Two concise sentences with the action front-loaded. No unnecessary words. Perfectly scoped for the information provided.

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 4 parameters, no output schema, no annotations, and sibling tools with related functionality, the description is too minimal. It fails to specify constraints like the valid range for 'count' or the format for 'size'. The return value is mentioned but not structured.

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% (no parameter descriptions in schema). The tool description does not explain any parameter meanings beyond their names. For example, it doesn't clarify that 'size' expects a format like '2048x2048' or that 'count' must be between 1 and 4.

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 action 'generate' on resource 'images' with specific details (1-4 images from a prompt, save locally, return paths). It distinguishes well from sibling tools like list_image_options (listing) and edit_image (editing).

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?

No guidance on when to use this tool versus alternatives such as edit_image or list_image_options. The description does not mention contexts, prerequisites, or exclusions.

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