create_workflow

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

No annotations are provided, so the description must cover behavioral traits. It states 'creates' and 'returns JSON', but does not disclose side effects (e.g., persistence, overwriting), authorization requirements, or whether the workflow is saved. This leaves some ambiguity.

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 with no wasted words. It front-loads the action and purpose, then lists templates and output. Highly efficient.

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 2-parameter tool with one required and no output schema, the description adequately covers purpose, available templates, and return value. It could mention whether 'params' is optional or how they affect the workflow, but overall complete enough.

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%, but the description adds meaning by listing example parameter keys for 'params' (e.g., checkpoint, positive_prompt), which the schema only marks as additionalProperties. This helps the agent understand what can be passed.

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 creates a ComfyUI workflow from a named template, lists all available templates, and indicates the output (complete workflow JSON). This distinguishes it from siblings like dsl_to_workflow or modify_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 description explicitly lists the six available templates, guiding when to use the tool. However, it does not mention when not to use it or compare with alternatives like modify_workflow or dsl_to_workflow.

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