comfyui_save_workflow

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the write action and the file location, and mentions a prerequisite (running the job once). However, it omits details about overwrite behavior, error conditions, or side effects beyond saving. It doesn't contradict any annotations (none 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?

Two sentences with no fluff. The main action is front-loaded, and the second sentence adds context about the use case. Every word contributes 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?

Given the tool's complexity (3 params, 0% schema coverage, no annotations), the description is incomplete. It doesn't explain parameter semantics, edge cases (e.g., overwrite behavior, existence checks), or error conditions. The presence of an output schema partially helps, but the description should provide more operational detail for an agent to use it 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 description coverage is 0%, so the description should compensate. It indirectly explains 'name' (file path) and implies 'prompt_id' (past job), but doesn't explicitly define either parameter. 'overwrite' is not addressed at all, leaving its purpose to inference from the boolean type. The description adds little beyond the schema's basic property types.

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 a specific action (save an API-format workflow), the resource (past job's workflow), and the destination (workflows/api/<name>.json). It also explains the workflow's role in converting UI-format to runnable, which distinguishes it from related tools like comfyui_convert_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 provides a clear usage context: run a job in the ComfyUI web UI, then save it from comfyui_history. It implies the tool is for post-run saving and references comfyui_history as the source. It doesn't explicitly list alternatives or when not to use, but the sequential hint is helpful.

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