comfyui_upload_image

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive nature (destructiveHint=false), which the description supports by stating it uploads. The description adds context about the input directory being the default and the intended use of output/temp, going beyond what annotations alone convey.

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 brief, front-loaded with the core action, and uses a bulleted list to convey important notes clearly. No redundancy or unnecessary detail.

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 simple nature of the tool, full schema coverage, and existing output schema, the description adequately covers what the tool does and key usage considerations. It includes practical destination guidance without needing to restate return values.

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?

The schema provides 100% description coverage for all parameters, including details about overwrite behavior and destination. The description does not add significant extra meaning, though it does highlight the destination parameter's context with 'destination workflows read from'.

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 opens with 'Upload an image to ComfyUI' which is a specific verb and resource, clearly distinguishing it from sibling tools like comfyui_upload_mask by name and function. It is concise and unambiguous.

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 guidance on when to use the default destination ('input') and advises setting other destinations 'only if you have a specific reason.' However, it does not explicitly discuss alternatives or when not to use this tool, such as when uploading a mask would be more appropriate.

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