save_workflow

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

With no annotations, the description fully covers behavioral traits: overwriting without confirmation, auto-conversion of API format, and return value details (confirmation or error). It also notes that the input is not validated before saving, adding transparency about potential issues.

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 a single well-organized paragraph that front-loads the main purpose, then covers prerequisites, side effects, format details, and return value. Every sentence adds necessary information without redundancy.

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?

Despite no output schema, the description fully explains the return value (confirmation with conversion notes or error). It also addresses prerequisites, side effects, and input format handling, making it complete for a tool with 2 parameters and a nested object.

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 100%, so baseline is 3. The description adds value by explaining the auto-conversion behavior for the 'workflow' parameter and reinforcing the overwrite behavior for 'filename', which goes beyond the schema's basic descriptions.

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 action ('Save a workflow JSON'), the resource ('to the connected ComfyUI server's user library'), and the outcome ('appears in the ComfyUI web UI'). It distinguishes itself from sibling tools like get_workflow or create_workflow by specifying the target and format handling.

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?

It explicitly states prerequisites ('Requires a running ComfyUI server') and warns about overwriting without confirmation. It provides clear guidance on when to use which format: UI format is preferred and saved as-is, while API format is auto-converted. It also suggests using get_workflow to load existing workflows before re-saving.

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