Inpaint Image

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Edit' implies mutation, it doesn't specify what kind of editing occurs, whether it's destructive to the original image, what permissions are required, or how the editing process works. The description lacks critical behavioral context for an image editing operation.

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 extremely concise at just 8 words, front-loading the core functionality with zero wasted words. Every element ('Edit specific regions', 'image', 'using a mask') contributes essential information about the tool's purpose and method.

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?

Given that there's an output schema (which handles return values) and 100% schema description coverage, the description is reasonably complete for its length. However, for an image editing tool with no annotations and multiple sibling tools, it should provide more context about when to use it and what the editing entails.

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 all 5 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions 'mask' which relates to 'maskUrl' and 'specific regions' which relates to the editing concept, but doesn't provide additional semantic context about parameter relationships or usage patterns.

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?

The description clearly states the action ('Edit specific regions') and resource ('image') using a specific method ('using a mask'). It distinguishes from siblings like 'create-variant' or 'generate-image' by focusing on editing existing images with masks rather than creating new ones. However, it doesn't explicitly differentiate from 'reroll-image' or 'upscale-image' which might also involve image modification.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'create-variant', 'reroll-image', and 'upscale-image' that might also modify images, there's no indication of when inpaint-image is appropriate versus those other tools. No prerequisites or exclusions are mentioned.

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