list_output_images

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

With no annotations, the description carries full burden. It discloses the output sorting order and the environment requirement. While it doesn't cover edge cases or error states, it adequately informs the agent of the tool's basic behavior for a simple read operation.

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 sentences with no wasted words. The main action is front-loaded, return format is second, and usage guidance with alternatives is in the third. Every sentence earns its place.

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 tool's simplicity (2 non-required params, no output schema), the description is fully complete. It covers purpose, output, prerequisite, and alternative tools for a different context. Handles the sibling tool landscape well.

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?

Both parameters have schema descriptions (100% coverage), so baseline is 3. The description adds value by stating the default behavior ('newest-first' sort order) and clarifying the pattern matching as 'case-insensitive substring match', which goes beyond the schema.

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 action ('list recently generated images'), specifies the resource ('ComfyUI's output directory'), and distinguishes the behavior ('returns filenames sorted newest-first'), which differentiates it from sibling tools like get_image or view_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?

Explicitly states the prerequisite ('Requires COMFYUI_PATH') and provides clear guidance for remote ComfyUI scenarios, directing the agent to use get_history and get_image instead. This effectively tells when and when not to use the tool, with alternatives named.

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