upload_image

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

Discloses the upload mechanism (HTTP /upload/image endpoint), storage location (input/ directory), and return value (stored filename). However, with no annotations provided, it fails to mention potential overwrite behavior, permissions, or side effects, leaving gaps in transparency.

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 with no redundant information. The first sentence immediately conveys the core purpose and mechanism. Every word earns its place.

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 simplicity of the tool (2 params, no output schema), the description adequately covers upload, storage, and return. Minor gap: no mention of overwrite behavior, but this is a simple utility tool.

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% and both parameters are described. The description does not add extra meaning beyond the schema; the return value note is not a parameter detail. Baseline 3 applies.

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'), resource ('local image file to ComfyUI's input/ directory'), and purpose ('so it can be referenced in LoadImage nodes'). Explicitly mentions the HTTP endpoint and distinguishes from sibling upload tools by specifying '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?

Provides context on where it works ('local and remote ComfyUI') but lacks explicit when-to-use, when-not-to-use, or comparisons to alternative upload tools (e.g., upload_audio, upload_video). No guidance on prerequisites or constraints.

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