comfyui_get_output

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

Annotations declare readOnlyHint=true, and the description adds meaningful behavioral details beyond that: files expose a streaming/seeking-capable url and, for media, a browser player page. It also discloses the include_temp behavior for temporary PreviewImage files, which is useful context not present in the annotations.

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 compact and front-loaded: the core purpose and output characteristics appear in the first sentence, followed by a concise args block. Every sentence earns its place, with no filler or repetition of schema information.

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?

For a simple two-parameter read-only list tool, the description covers the key context: when to call it, how to identify the job, and what the returned files look like. It could mention behavior when the job is not finished or when no outputs exist, but given the annotations and simplicity, it is largely complete.

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%, so the description carries full responsibility for parameter meaning. It explains prompt_id as the job id returned by comfyui_run or a preset tool, and include_temp as a flag for temporary preview files, adding real semantics beyond the raw schema types and defaults.

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 opens with a specific verb and resource: "List the files produced by a finished job," and enumerates file types (images, videos, audio). This clearly differentiates it from sibling tools like comfyui_job_status or comfyui_history by focusing on retrieving output artifacts rather than job state or workflow metadata.

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 specifies when to use the tool: after a job is finished, using a prompt_id returned by comfyui_run or a preset tool. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to know this is the retrieval step after job completion.

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