save_workflow

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

With no annotations, the description carries the full burden. It discloses critical behavioral traits: the tool overwrites without confirmation, stores workflow verbatim without validation, and accepts both API and UI formats. It also specifies failure behavior (HTTP status and error text). This is transparent and sufficient for safe use.

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 extremely concise: 4 sentences covering purpose, prerequisites, behavior, accepted formats, and return value. It is front-loaded with the main action and each sentence adds essential information without redundancy or fluff.

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 covers return values ('confirmation message or error). It explains the overwrite behavior, format flexibility, and need for a running server. The tool is straightforward, and the description provides enough context for correct invocation, though the exact confirmation format is left unspecified.

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%, so the baseline is 3. The description adds limited extra value: it notes 'Stored verbatim; not validated before saving' for the workflow parameter, but the schema already mentions accepted formats. The filename parameter's overwrite behavior is already in the schema. Thus, minimal addition beyond 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 verb ('Save') and resource ('workflow JSON'), specifies the target ('user library') and effect ('appears in the web UI'), and distinguishes itself by mentioning specific formats (API/UI) and overwrite behavior, differentiating it from sibling tools like 'create_workflow' which likely creates new workflows.

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 prerequisite ('Requires a running ComfyUI server') and warns about overwriting, but does not explicitly guide the agent on when to use this tool versus alternatives (e.g., 'create_workflow', 'modify_workflow'). The context of 'so it appears in the web UI' implies the use case, but lacks comparative guidance.

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