nano_banana_generate_image

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

No annotations are present, so the description carries the full burden. It discloses the core dual function (generate or edit) but does not mention authentication, output behavior, side effects, rate limits, or reference-image handling.

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?

A single, front-loaded sentence with no filler. It immediately communicates the action and resource, making it highly scannable and efficient.

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?

Despite having an output schema, the tool is complex (6 parameters, auth modes, model choices, reference images) and the description is too terse to support correct invocation. It omits guidance on model selection, authentication, and use of reference images for editing.

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% and the description does not mention any of the 6 parameters. It does not compensate for the lack of documentation around prompt, output_path, model selection, auth_mode, or reference_image_paths.

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 states a specific action ('Generate or edit an image') tied to a concrete resource ('Google's Nano Banana Gemini image models'). It clearly distinguishes this tool from video-focused siblings like veo_generate_video and stitch_videos.

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 implies use for image generation/editing vs video tools, but it does not explicitly state when to use this tool or its alternatives. No exclusions or conditions are provided.

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