list_output_images

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

Without annotations, the description fully discloses behavior: recursive filesystem scan on local, /history-based derivation on remote (noting missing size/modified), and that it returns metadata not bytes. Ends with 'Read-only'.

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?

Somewhat lengthy but efficiently packed with all necessary details. Front-loaded with main purpose, and structure is logical.

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?

No output schema, but description explains return fields (kind, subfolder, size, modification time). Covers local vs remote behaviors, file types, and use case. Complete for a listing 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% with descriptions for both parameters (limit, pattern). The description adds usage context but does not significantly enhance understanding beyond what the schema already provides.

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 lists recently generated image and video files from ComfyUI's output directory, newest-first, with specific file types. It distinguishes between local and remote ComfyUI and explicitly states it does not return media bytes, referencing get_image. This sets it apart from siblings like get_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 explicit guidance: 'USE THIS TO CONFIRM A VIDEO RENDER...when get_history shows the prompt done but lists no output' and suggests chaining with stage_output_as_input. It also contrasts with get_image, making clear when to use each.

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