list_assets

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

The description discloses the behavioral scope: it lists models and media files from the input folder, implying read-only access. With no annotations, this is valuable context. It doesn't explicitly state 'read-only' or return format, but the description adequately conveys the tool's behavior for a simple list 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?

The description is a single, front-loaded sentence that immediately states the action and scope. Every word earns its place with no 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?

For a zero-parameter discovery tool, the description is complete: it fully explains what assets are returned and that they are usable by name. No output schema or annotations are needed, and the description provides sufficient context for an agent to decide when to invoke it.

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 has zero parameters, so the baseline is 4. The description compensates by clarifying what will be listed, which is the only relevant semantic context.

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 (loadable assets: H3 models, images, videos, audio in the input folder). It also distinguishes itself from sibling tools by focusing on asset inventory rather than job management or generation.

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 clearly establishes when to use the tool (when you need to know what ComfyUI can load). It does not explicitly mention alternatives, but sibling tools are obviously job-oriented, so context is sufficient without explicit exclusions.

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