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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description must carry nuance, and it does add one concrete behavioral constraint: the provider field must not be sent because the model is pinned by the API. It says nothing about cost, latency, or whether generation is synchronous or returns a task handle for polling (a real concern given the sibling nexscope_media_task_result).

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 sentences, front-loaded with the capability and followed by the one hard constraint. No filler, though the second sentence could have been folded in more smoothly and there is room left unused for differentiating context.

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?

No output schema exists, so the description should say what comes back (image URLs, task ID, count based on outputNum) and it does not. Parameters and safety hints are covered by schema and annotations respectively, but for a paid, open-world generation call the result contract is a meaningful omission.

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 schema already documents prompt limits, the 1–14 reference image rule, file types/sizes, outputNum and the resolution/aspectRatio enums. The description adds no parameter meaning beyond the provider-exclusion note, so baseline 3 applies.

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?

States a specific verb pair (generate and edit) with a concrete resource (ecommerce images) and names the exact model version, which is essential given siblings nexscope_banana_2_image_generation, nexscope_banana_2_lite_image_generation, nexscope_banana_image_generation and nexscope_banana_pro_image_generation. The 'improved text layout and consistency across editing rounds' phrase hints at why this variant exists, but it never explicitly says how it differs from the other banana variants an agent must choose between.

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 only explicit usage rule is a negative one: do not supply a provider because the model is fixed. Nothing tells the agent when to pick 2.1 over the lite/2.0/pro banana siblings or over text-to-image tools like nexscope_wan_2_7_image_generation; usage is implied by the 'ecommerce images' framing rather than stated.

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