comfy_upload_image

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

Annotations declare readOnlyHint=false, and the description reinforces this by stating 'Upload an image to ComfyUI,' implying a write operation. It adds useful detail about the 'subfolder' parameter (optional directory placement) and 'overwrite' flag (defaults to false), but does not discuss authorization requirements, storage limits, or any side effects beyond file creation. No contradiction with annotations.

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: a one-line purpose and a clean Args block for four parameters. No fluff, no redundancy with the schema, and the structure is easy to parse.

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?

The description covers the essential operation but omits context like return value (what happens on success—does it return a URL, a path?), error handling, and prerequisites (e.g., ComfyUI must be running). Since the schema includes a title and required fields, it's not incomplete, but it lacks operational details that could prevent misuse. Among a large set of comfy_* tools, this one's scope is narrow and largely self-explanatory.

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 description provides a brief explanation for each parameter, but lacks specifics like allowed image formats, maximum file size, or filename constraints. The schema itself has no parameter descriptions (0% coverage), so the description fills that gap but doesn't go into detail. For example, it doesn't clarify whether image_data must be base64-encoded data URI or raw base64, or what subfolder structure is expected.

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 is concise and specific: 'Upload an image to ComfyUI' clearly identifies the action (upload), the resource (image), and the destination (ComfyUI). It distinguishes from sibling tools like comfy_get_artifact (retrieval) or comfy_queue_prompt (execution), making the purpose 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 does not provide explicit guidance on when to use this tool versus alternativesholistically. It doesn't mention when not to use it, nor does it reference related tools like comfy_import_workflow or comfy_download_model. The context of uploading an image is clear, but exclusions or alternative suggestions are absent.

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