comfyui_list_workflows

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

Annotations already convey read-only and safe behavior, and the description adds valuable context: the exact endpoint, the paginated response envelope, and the per-item structure. This goes beyond the schema and annotations to set accurate expectations about the return payload.

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 well-organized into four concise sentences, each serving a purpose: listing the core action, giving endpoint context, distinguishing from a sibling, and describing the response. No filler or redundancy is present.

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, strong annotations, complete parameter schema, and presence of an output schema, the description fully covers what an agent needs to select and invoke it correctly. It explains the source, the distinction from related functionality, and the return shape.

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% for limit and offset, so the baseline applies. The description mentions pagination and the response envelope, which indirectly relates to these parameters, but it does not add detail beyond what the schema already provides. It is adequate but not additive.

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 states a specific verb and resource: 'List workflow templates registered on the ComfyUI server.' It also distinguishes this from comfyui_create_workflow's hard-coded template names, which prevents confusion with a sibling tool. The intent is unmistakable.

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?

It explicitly calls out the difference from comfyui_create_workflow's built-in templates, giving the agent a clear rule for when to use this tool instead. The endpoint context ('/workflow_templates', populated by installed packages) also clarifies the tool's scope.

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