generate_image

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

With no annotations provided, the description carries the full burden. It discloses that it uses saved authentication, bypasses chat quotas, and supports upscale. It notes the 'Ultra' requirement for 4K. However, it omits rate limits, costs, and error behavior, preventing a higher score.

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 a single dense paragraph, but it is well-structured and front-loaded with the core purpose. It packs significant detail without extraneous words. Could be slightly improved by using bullet points for readability, but it remains concise and informative.

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 6 parameters (1 required), 2 enums, and an output schema (true), the description covers the essential functionality, parameter options, and quirks like the Ultra requirement. It lacks details on return values, but the output schema likely covers that. Minor gaps in error handling or batch limitations prevent a perfect score.

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%, so the description must compensate. It adds substantial meaning: explains `count` as number of images, lists model options with defaults, interprets `aspect` ratios, clarifies `resolution` defaults and options (1k, 2k, 4k), and describes `reference_image` for image-to-image. This fully compensates for the lack of schema descriptions.

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 it generates images via Google Flow's batchGenerateImages API, lists supported modes (text-to-image and image-to-image), and details models, aspects, and resolutions. It clearly distinguishes itself from the Flow Agent chat quota by noting it bypasses that limitation, making the purpose unmistakable.

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 provides clear usage guidance, such as bypassing the chat quota and requiring 'Ultra' for 4K. It details options without ambiguity. However, it does not explicitly state when not to use this tool or mention alternatives, though no sibling tools exist. Slight room for improvement.

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