save_workflow

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

With no annotations, the description covers key behaviors: it writes to server userdata, overwrites without confirmation, accepts both JSON formats, and does not validate. This is transparent and provides essential side-effect information, though it could mention return format in more detail.

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 three sentences with no redundant information. It front-loads the core purpose, then covers prerequisites/behavior, and finally return values. Every sentence adds necessary context.

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 output schema, the description adequately explains return values (confirmation message or error with status). It addresses prerequisites, side effects, and input format flexibility, making it complete for the tool's complexity.

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 schema already provides descriptions for both parameters (100% coverage). The description adds value by clarifying the workflow parameter accepts API- or UI-format JSON and that filename will overwrite existing files, enhancing semantic understanding beyond the schema.

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 saves a workflow JSON to the ComfyUI server's user library, specifying both the action (save) and the resource (workflow JSON to user library). It distinguishes from siblings like upload_image or create_workflow by focusing on saving existing workflows to a persistent location visible in the web UI.

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 mentions a prerequisite (requires running ComfyUI server) and warns about overwriting without confirmation. However, it does not explicitly specify when to use this tool over alternatives like create_workflow or upload_workflow, nor does it provide exclusions or guidance on when not to use it.

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