generate_asset

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

With no annotations, the description must carry behavioral disclosure on its own. It does disclose supported inputs and output types at a high level, such as reference images, color palettes, logos, aspect ratios, and 2K/4K resolutions. It does not disclose output format, side effects, costs, or failure modes, so transparency is adequate but not rich.

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 two sentences with no filler. The core purpose is front-loaded, and the capability list is compact and useful. Every sentence earns its place.

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 7-param tool with no annotations and no output schema, the description is reasonably complete: it summarizes capabilities and defers parameter details to the schema. However, it does not explain what the tool returns (URL, base64, file path), nor does it provide any guidance about edit vs generate workflows, leaving some practical gaps.

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 100%, so the baseline is 3. The description reinforces some parameters by mentioning reference images, color palettes, logos, aspect ratios, and resolutions, but it adds no meaning beyond the schema for parameters like editInstructions. It does not need to compensate much because the schema is already detailed.

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?

Purpose is immediately clear: 'Generate a single web asset using Nano Banana Pro' names a specific verb, resource, and scope. The phrase 'single' distinguishes it from the sibling generate_asset_pack, and listing asset types (icons, banners, backgrounds, UI elements) further aids selection.

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 the tool is for creating one new asset, which hints at when to use it over generate_asset_pack or edit_asset. However, it never explicitly says when not to use it, nor does it mention alternatives by name, leaving the routing decision partially to inference.

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