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

Annotations only declare openWorldHint=true, so the description carries most of the behavioral burden. It usefully discloses the async pattern (returns a request ID, results retrieved via fetch-image), but omits cost/latency, auth requirements, and what happens to the original image. This partial disclosure is adequate but thin.

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?

Three tight sentences with the core action front-loaded, followed by input semantics and the async return path. No filler or repetition of schema content.

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?

With no output schema, the description appropriately explains that the immediate return is a request ID and that fetch-image retrieves the result, closing the main gap for an async tool. Coverage is nearly complete, missing only edge conditions such as failure or timeout behavior.

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% across 11 parameters, including ranges and defaults, so the schema does all parameter work. The description adds no extra meaning about strength, samples, or negative_prompt beyond what the schema already says, giving the baseline 3.

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 ('Transform existing images based on text prompts') and clarifies that an input image is modified, which implicitly separates it from text-to-image. It stops short of naming the closest siblings (text-to-image, inpaint-image, image-to-video), so an agent must infer which one fits.

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 mention that the returned request ID is used with fetch-image gives a clear downstream routing hint, and 'takes an input image' implies usage. However, there is no explicit when-to-use vs when-not guidance relative to text-to-image or inpaint-image, which are the natural alternatives.

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