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

Annotations only declare readOnlyHint=false and openWorldHint=true, and the description does add one genuinely useful constraint beyond them: the model is fixed, so 'provider' must not be sent. But it omits the behavior an agent most needs -- whether this is synchronous or returns a task ID for nexscope_media_task_result, and whether generation is billed/rate-limited.

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, front-loaded with the capability and followed by the single non-obvious request constraint. Nothing is repeated from the schema and no filler remains.

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 mutation-style generation tool with no output schema and thin annotations, the description leaves critical gaps: return shape (URLs vs. task ID), any follow-up call needed, expected latency, and how to choose among the crowded banana/gpt-image family. The agent can construct a request but cannot predict the outcome.

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%: prompt limits, imageUrls count/size/format, outputNum range, resolution and aspectRatio enums are all documented in the schema. The description adds nothing parameter-level except confirming the model is not a parameter, 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 and resource ('Generate higher-resolution ecommerce images') and names the governing model, so the agent knows this is text/image-to-image generation. It only weakly differentiates from the many sibling banana/gpt-image generators -- 'higher-resolution' and 'Pro' imply a quality tier but never explicitly contrast with nexscope_banana_2_1_image_generation or nexscope_banana_2_image_generation.

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 routing signal is 'higher-resolution ecommerce images'; there is no statement of when to pick this over the five other banana variants or over nexscope_seedream_5_pro_image_generation. No prerequisites, no when-not-to-use, no mention of downstream task polling.

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