text_to_image

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

With no annotations, the description carries the full burden; it does add real value by disclosing the async task model and the return payload (task id, status, output URLs), which compensates for the absent output schema. However, it omits the default polling behavior of 'wait', timeout semantics, and cost/auth implications that the check_pricing and login siblings hint at.

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?

Two tight sentences with the action and the return shape front-loaded, and no filler. It is efficient, though arguably too short given the tool's 10-parameter surface.

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?

For a 10-parameter, zero-required, annotation-free asynchronous generation tool with no output schema, the description is far too thin. It explains the result payload but leaves the async lifecycle, model/quality options, and optional inputs such as reference_image_urls and callback_url entirely to the schema.

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 only 20% across 10 parameters, so the description is expected to compensate, and it does not — prompt, model selection, aspect_ratio, reference_image_urls, callback_url, and output_format are all left unexplained. The only text offered concerns the return value, not the inputs.

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?

Specific verb ('Create') plus resource ('Nano Banana task') and the parenthetical '(text to image)' separates it from the sibling edit_image, which implies image-in/image-out. It is clear what the tool produces, though it never names edit_image as the contrasting alternative.

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?

There is no guidance on when to choose this over edit_image, nor any mention of the async workflow the schema implies (wait defaults to true, otherwise the sibling get_task must be polled). The agent must infer all usage conditions from the schema.

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