upload_image

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

Discloses dual upload strategy (HTTP first, filesystem fallback) and the condition (COMFYUI_PATH set). No annotations provided, so description carries full burden. Missing details like overwrite behavior or supported formats but sufficient for basic usage.

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?

Two sentences, front-loaded with purpose, then implementation detail. No fluff, though could be slightly restructured for readability.

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 no output schema and simplicity of upload, description covers main purpose and fallback. Could mention file size/type constraints but adequate for selection and invocation.

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 coverage is 100%, but description adds value: explains auto-detection of filename and that source_path is absolute. Also provides context on the upload mechanism beyond schema.

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?

Clear verb ('Upload') and resource ('local image file to ComfyUI's input/ directory'), with specific purpose ('referenced in LoadImage nodes'). Distinguishes from siblings like download_model or get_image.

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?

Description mentions fallback behavior but lacks explicit when-to-use or when-not-to-use guidance. No alternatives for uploading images are discussed.

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