list_workflows

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

With no annotations, description covers precondition (running server), output format (numbered .json filenames), and empty case message. Does not explicitly state non-destructive nature but infers safety. Adequate for a simple read-only list.

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?

Three concise sentences, front-loaded with purpose. No redundant information; every sentence adds value.

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?

Fully describes input (none), output format, edge case (empty library), and how to use the result with sibling tools. No output schema needed as return value is clearly described.

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?

Zero parameters; schema coverage is trivially 100%. Description confirms 'Takes no parameters,' adding no ambiguity. Baseline score of 4 is appropriate.

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?

Clearly states it lists filenames of workflows from the ComfyUI server's user library, mirroring the web UI. Differentiates from siblings by specifying that output filenames can be passed to get_workflow or analyze_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?

Explicitly mentions requirement of a running ComfyUI server and that it takes no parameters. Implicitly guides usage by linking output to sibling tools, but lacks explicit when-not-to-use guidance compared to other list tools.

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