comfyui_list_models

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

With no annotations, the description carries the full burden but it only discloses the dual-mode behavior (folders vs models in a folder). It does not mention read-only status, error handling, or sorting, although 'List' implies a read operation and the output schema can cover return format. This is adequate but not rich.

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 zero unnecessary words. It efficiently conveys the tool's scope and the optional behavior without redundancy.

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 (one optional parameter) and that an output schema exists, the description covers the primary behaviors. It lacks explicit parameter-to-mode mapping (e.g., 'omit to list folders') but this is easily inferred. Edge cases are not discussed, but overall it is sufficient for basic invocation.

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 0%, so the description must compensate. It does by explaining that the optional 'folder' parameter selects between listing folders (omitted) or models within a specific folder, and gives concrete examples ('checkpoints', 'loras'). This adds meaning beyond the bare 'folder' property name.

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 uses a specific verb ('List') and clearly identifies the resource ('ComfyUI model folders' or 'models within one folder'). It provides examples ('such as checkpoints or loras') and distinguishes itself from sibling list tools (node types, templates, workflows).

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 gives clear context: it can list top-level folders or models inside a named folder, with examples of valid folder values. It does not explicitly state when not to use it or mention alternatives, but the purpose is unambiguous enough for an agent to select it appropriately among siblings.

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