List Models

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

No annotations exist, so the description carries the burden; it does convey that this is a pure enumeration with no mutation of files. However, it says nothing about whether the results reflect on-disk models vs. loaded models, whether the server must be reachable, or how the two resources are separated in the response.

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?

A single front-loaded sentence with no filler; both returned resource types are named up front. Every word 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?

With no parameters and an output schema present, the description needn't explain the return shape, and it correctly identifies what is listed. The only missing piece is the operational precondition (a reachable ComfyUI server) and the distinction from server_status.

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 tool takes zero parameters, so the baseline is 4 and there is nothing further the description needs to document. Nothing in the description conflicts with the empty 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?

States a specific verb ('List') plus two concrete resources: the server's workflows and the model files ComfyUI can see. An agent can tell this is a discovery/enumeration call, though it never explicitly contrasts itself with the similarly-named sibling server_status or unload_models.

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?

Usage is only implied — an agent can infer this is the discovery step before generate_image or edit_image, but the description never says when to call it, when not to, or which sibling covers overlapping information. No prerequisites (e.g. server must be running) are noted.

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