create_workflow

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

With no annotations, the description fully discloses behavior: pure local generation, no side effects, does not contact ComfyUI, returns JSON, and notes that missing params use defaults which may reference models that must exist.

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?

Description is thorough but efficient: front-loaded with purpose and templates, then behavioral context, then usage guidance. Every sentence contributes meaningful information without unnecessary repetition.

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?

Comprehensive for a tool with no output schema: explains return value (complete workflow JSON), notes model dependencies, and covers the complexity of multiple templates and parameter fallback behavior. Fully prepares an agent to use the tool correctly.

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 already covers parameters; description adds value by listing common template-specific keys (e.g., checkpoint, positive_prompt for txt2img) and clarifying that unknown keys are ignored. This helps agents construct valid parameter objects.

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?

Explicitly states the tool creates a ComfyUI workflow from a built-in template, lists all template options, and distinguishes from siblings by noting the output should be passed to validate_workflow or enqueue_workflow for execution.

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?

Clearly describes when to use (creating a workflow from a template) and what to do with the result (validate or enqueue). Does not explicitly state when not to use, but context from sibling tool names makes alternatives clear.

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