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

No annotations exist, so the description carries the behavioral disclosure burden. It adds important facts beyond the obvious generation behavior: it is an async task that must be polled via get_task, listed models can be free within a shared daily fair-use pool, and otherwise credit consumption occurs. This gives the agent material guidance about side effects and follow-up.

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 compact and front-loaded; the first sentence establishes the core operation and the second covers economic/blob behavior and result polling. It is slightly dense, but the factual content 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 an async generation tool with no output schema, it properly tells the caller how to retrieve results via get_task and indicates nudget that lit consumed pricing can be 0. It does not specify output fields, failure behavior, quality, or aspect_ratio constraints, but an agent has enough to invoke it correctly and retrieve results.

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 0 percent, so the description must compensate. It does add meaning for image_urls by explaining that providing them switches the task to image-to-image, and it offers example model names. However, scene, quality, prompt, and aspect_ratio have no described effect or allowed values, leaving several use issues unresolved.

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 precise verb and resource: it creates an image generation task. It also distinguishes between text-to-image and image-to-image modes depending on image_urls, making it clearly distinct from sibling tools like generate_music, generate_ideo, or generate_speech.

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?

Clear context is present: it is the image-generation tool, and image-to-image is the correct mode when image_urls are provided. It also tells the caller to poll get_task for the eventual result URLs. It does not explicitly list when not to use it in favor of a sibling, but the image-specific wording makes the intended usage effectively unambiguous.

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