Nano Banana 2 Official

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

With no annotations, the description explains preset ownership, override behavior, and enum usage. However, it omits details like authentication requirements, error responses, or side effects beyond invalid sizes.

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?

Six sentences effectively convey the main purpose and key behavioral notes without excessive verbosity. The primary function is front-loaded.

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 tool's complexity (12 parameters, no schema descriptions), the description is insufficient. It covers preset semantics and enum usage but neglects many parameters, error handling, and return values, even with an output schema present.

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?

With 0% schema description coverage, the description only partially compensates by explaining preset, api_key, image_size, and aspect_ratio relationships. The other 8 parameters lack any added meaning.

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 it generates or edits images via a Gemini compatible gateway. It provides a specific verb and resource, though it does not explicitly distinguish from sibling tools like gpt_image_2_official.

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. The description focuses on preset behavior but lacks explicit 'when-not' or alternative tool references.

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