generate_image

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

No annotations are provided, so the description carries the full burden. It only says 'generate an image' and does not disclose side effects like file saving (default output directory), the possibility of returning base64, model-specific restrictions (e.g., 0.5K only for Flash), or any failure modes. The schema mentions outputDir and returnBase64, but the description itself adds no behavioral transparency.

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, front-loaded sentence that immediately states the verb and resource. It contains no filler or redundant explanation, making it appropriately concise for the information it conveys.

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 the lack of annotations and output schema, the description should clarify success outputs (e.g., saved file path vs. base64) and model selection guidance. It does neither, leaving the agent to rely entirely on schema descriptions. While the schema is rich, the tool-level context is incomplete for confident invocation.

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 descriptions cover all 6 parameters at 100% with meaningful details (model enum, resolution, aspect ratio, output options). The description merely repeats model names already present in the schema, adding no new parameter semantics beyond the structured fields.

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 a specific verb ('generate') and resource ('image') with relevant model context (Nano Banana 2 or Nano Banana Pro). It does not explicitly differentiate from sibling tools like batch_generate or generate_variations, but the core purpose is unambiguous.

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 is provided on when to use this tool versus alternatives such as edit_image or generate_variations. The description gives no context for model selection or ideal use cases, leaving the agent to infer usage from sibling names and schema enums.

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