list_workflows

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

Despite no annotations, description discloses output format ('numbered list of .json filenames'), edge case ('Returns No saved workflows found. when library is empty'), and implicitly read-only nature. No contradictions.

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 with no redundancy. Each sentence adds unique value: purpose, prerequisites/parameters, output/edge case.

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?

Complete for a simple list tool: covers purpose, prerequisites, parameters, output, and edge case. No gaps given lack of annotations or output schema.

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 has 0 parameters with 100% coverage. Description confirms 'Takes no parameters', adding no extra meaning but reinforcing schema. Baseline score of 3 applies.

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 verb 'list' and resource 'filenames of workflows saved in the connected ComfyUI server's user library'. Distinguishes from siblings like get_workflow and analyze_workflow by noting they take a filename parameter.

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?

Mentions prerequisite 'Requires a running ComfyUI server' and context for using output: 'pass a filename to get_workflow or analyze_workflow to load one'. Could be more explicit about when not to use, but provides good guidance.

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