comfyui_list_workflows

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

With no annotations, the description carries the full burden. It discloses the read-only nature through the verb 'list' and mentions the included data (revision and node counts), but does not discuss pagination, error conditions, or other behavioral traits. It adds some value but lacks richer context.

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, focused sentence with no filler. It efficiently conveys action, scope, and output highlights.

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, straightforward list operation with an output schema, the description covers the essentials. It could include usage guidance, but the simplicity of the tool lowers the bar for completeness.

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 and an empty schema, so the baseline is 4. The description does not need to add parameter detail, and its mention of returned fields is a bonus, though not directly parameter-related.

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' and the resource 'workflows managed by this MCP server,' and adds specific output details (revision and node counts). This distinguishes it from sibling tools like comfyui_list_models or comfyui_get_workflow.

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 usage is implied: it lists all workflows, so it would be used when an overview is needed. However, there is no explicit statement of when to use it versus alternatives, nor any exclusions or alternative tool mentions, so it does not meet the 'explicit guidance' bar.

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