prepare_image_for_workflow

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

No annotations are supplied, so the description carries the whole burden, and it does disclose the important side effect: it uploads into the ComfyUI input folder, and it requires COMFYUI_HOST. It does not explain what happens if the prompt has no image, or whether an existing file with the same name is overwritten.

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?

Three short sentences that open with the action and the side effect, then state the return value, then the precondition. Nothing is repeated and nothing is wasted.

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?

With one required parameter and no output schema, the description fills the return-value gap by naming the filename to use in LoadImage, and it names the follow-up workflow context. Only edge cases (no image present, filename collision) are 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?

The schema documents prompt_id at 100% coverage, and the description adds meaning on top of it: the id comes from execute_workflow, and the run must already be completed with image output. For a tool with a single parameter, this is as much semantics as an agent needs.

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 states a specific verb and resource: it fetches the first output image from a completed prompt and uploads it to the ComfyUI input folder, returning the filename. That sequence is clearly distinguishable from siblings such as download_output/get_last_output, which retrieve files rather than staging them for a 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?

"Use after get_execution_status confirms the prompt finished with image output" gives an explicit precondition and names the sibling to check first. The text does not say when not to use this tool or which alternative to pick when only downloading is needed, so it falls short of a full advisory.

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