comfyui_inpaint_image

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

The description adds the useful precondition about prior uploads and clarifies mask semantics. However, it does not disclose asynchronous behavior or output handling beyond what the 'wait' parameter already describes. Annotations include readOnlyHint=false and destructiveHint=false, and the description does not contradict these, so the additional behavioral context is moderate.

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 short and front-loaded with the main action. The three sentences are efficient, though the mask white-region note slightly duplicates the schema's parameter description. Overall, it is concise and structured logically: purpose, prerequisite, mask interpretation.

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 the tool's complexity (9 params, output schema present) and annotations, the description provides the essential operational context: the upload prerequisite and mask meaning. The wait behavior and model selection are covered by the schema. This is adequate for a well-documented tool, though a note about asynchronous default could further improve completeness.

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?

Input schema has 100% description coverage across all 9 parameters. The tool description mostly reiterates mask semantics ('White regions in the mask indicate areas to regenerate') that are already in the schema. Since the schema fully documents each parameter, the description adds minimal extra parameter-level meaning.

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 begins with a specific verb+resource: 'Inpaint regions of an image using a mask and text prompt.' This clearly defines the tool's purpose and distinguishes it from sibling image tools like comfyui_generate_image or comfyui_upscale_image by emphasizing mask-based inpainting.

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 a clear prerequisite: both image and mask must already be uploaded via comfyui_upload_image/comfyui_upload_mask. This tells the agent the necessary setup step, though it does not explicitly mention when not to use this tool or when an alternative like comfyui_transform_image would be preferred.

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