comfyui_download_output

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

With no annotations available, the description must disclose behavioral details, but it only states the core action. There is no mention of side effects (e.g., file overwriting, directory creation), permission requirements, or what the tool returns after downloading.

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, focused sentence with no wasted words. It front-loads the action and destination, making it easy to scan, though the extreme brevity limits the information it can convey.

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 tool has 4 parameters, an output schema, and no annotations, so the description needs to provide substantial context. It only covers the high-level action, leaving parameter semantics, behavioral expectations, and usage context entirely unaddressed.

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 mention any of the four parameters (filename, prompt_id, subfolder, output_type). The agent gets no additional meaning beyond the raw parameter names and defaults, which is insufficient for a tool with an optional prompt_id and multiple output options.

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 specifies the action ('Download') and the resource/destination ('generated ComfyUI file into this server's managed output directory'). It distinguishes the general direction from sibling tools like comfyui_upload_image, though it does not explicitly compare itself to alternatives.

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?

No guidance is provided about when to use this tool versus related tools such as comfyui_get_run or comfyui_upload_image. It lacks prerequisites, typical use cases, or any caveats about when not to use it.

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