comfyui_upload_image

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

No annotations are provided, so the description must communicate behavior. It mentions 'allowed' (suggesting restrictions) but does not explain what happens with disallowed files, overwrite semantics, or side effects. The tool's mutation behavior (uploading a file) is clear but lacks detail.

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 a single, front-loaded sentence with no filler. Every word contributes to the core purpose, making it highly concise.

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 a tool with 3 parameters, no schema descriptions, and no annotations, the description is too sparse. It fails to explain how to specify file paths, what 'allowed' means, or how overwrite and subfolder interact. The existence of an output schema does not compensate for missing parameter and behavioral detail.

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%, and the description does not explain any of the three parameters. file_path, overwrite, and subfolder semantics are left entirely to inference from names, which is insufficient for an agent to invoke correctly.

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 (upload), the object (local image), and the destination/purpose (ComfyUI for LoadImage-style nodes). This distinguishes it from sibling tools like comfyui_list_models or comfyui_run_workflow.

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 phrase 'for LoadImage-style nodes' implies when to use this tool, but it does not explicitly state when not to use it or provide alternative tools. No prerequisites or workflow context are given.

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