generate_image

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

No annotations provided, but the description discloses the auto-expansion behavior when 'enhance' is True and explains the style behaviors. It also states the output format (PNG file paths). Does not cover auth or rate limits, but reasonable for this tool.

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 well-structured with clear sections for aspect ratios and styles, but somewhat long. Core purpose is front-loaded. Could be slightly more concise by moving style details to secondary position.

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 and 6 parameters, the description covers input, key behaviors, and output format. Missing details on aspect format constraints and error handling, but generally complete.

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 has 0% description coverage; the description compensates by explaining 'prompt', 'aspect' with examples, 'enhance', 'style'. However, 'out_dir' is not explained, and 'n' is only implicitly mentioned.

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 generates image(s) from a text prompt with given aspect ratio and returns PNG file paths. It distinguishes from sibling tools like 'styled_deck' which are deck-focused.

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 when to use 'enhance' and describes specific styles ('slide', 'fintech'), but does not explicitly state when not to use this tool or compare to alternatives like 'styled_deck'.

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