save_output

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

The description adds important behavioral context beyond annotations: it explains that ComfyUI's save nodes cannot write to absolute paths, necessitating this relocation step. It also states the return structure ({saved_paths, dest_dir}). Annotations (readOnlyHint=false, openWorldHint=true) are consistent with this write-and-copy operation; no contradictions.

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 well-structured and front-loaded with the core purpose. Each sentence adds value, but it could be slightly more concise, particularly the second paragraph which lists options in a slightly verbose manner.

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 complexity (7 parameters, no schema descriptions, but an output schema), the description covers the main workflow and return value. It lacks details on overwrite and subfolder/type usage, but the output schema and the mention of 'as reported in a run's outputs' provide enough context for an AI agent.

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 adds meaning beyond the schema for key parameters (prompt_id, filename, dest_dir, dest_filename), which is critical given 0% schema description coverage. However, parameters like type, subfolder, and overwrite are only mentioned in passing or not explained, leaving some ambiguity.

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 states the tool's purpose: copying finished renders from ComfyUI's output tree to a reachable folder. It explains the underlying reason (ComfyUI's save nodes are restricted) and distinguishes this tool from siblings like view_output or upload_image by focusing on file relocation.

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 provides clear usage guidance: use either prompt_id or explicit filename+subfolder/type, and explains defaults for dest_dir and dest_filename. It does not explicitly mention when not to use the tool or alternatives, but the guidance is sufficient for correct invocation.

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