list_workflow_templates

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

Without annotations, the description discloses important behavioral traits: it hits the live server API, lists grouped by source, and cannot load templates headlessly. It adds context beyond the schema. Good transparency for a read-only list tool.

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 two sentences, but the second sentence is lengthy and packs multiple pieces of guidance. It is efficient but slightly dense. Still, it earns its place with useful information.

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 no parameters, no output schema, and no annotations, the description covers purpose, usage guidelines, and limitations well. It could mention return format but is complete enough for an agent to decide when to call.

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 description needn't add parameter info. Per guidelines, 0 params baseline is 4. Schema coverage is 100% trivially, no additional param info needed.

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 tool lists official ComfyUI workflow templates grouped by source. It uses specific verb 'list' and resource 'official ComfyUI workflow templates', distinguishing it from sibling tools like list_skills and list_packs.

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?

Explicit guidance is provided: 'When asked to set up/build a workflow, check here for a matching official starter template AFTER checking list_skills/list_packs'. Also notes limitation about loading onto canvas, giving clear when-to-use and when-not-to-use context.

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