comfy_save_technique

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description carries most of the behavioral burden. The description does not disclose side effects such as whether saving overwrites an existing technique, whether it validates the workflow, or how the technique is stored. It only lists parameters, not behavior.

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 appropriately brief and structured with a summary line followed by an Args list. Every sentence contributes value, though the Args explanations could be slightly more informative. It is efficient without being overly terse.

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?

For a save operation with an output schema, the description covers parameter semantics adequately. However, it omits important behavioral context such as overwrite behavior, persistence details, or whether the workflow must conform to a specific format. With four parameters and a nested object, a bit more guidance would improve completeness.

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 compensates by listing all four parameters with brief definitions: 'workflow dictionary', 'name for the technique', and optional description/tags. This adds meaning beyond the bare schema, but it lacks deeper constraints, examples, or required format details.

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's function: 'Save a workflow as a reusable technique.' This uses a specific verb ('Save') and a specific resource ('workflow as a reusable technique'), distinguishing it from sibling tools like list_techniques, search_techniques, and replay_technique.

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 purpose implicitly suggests when to use this tool (when you want to reuse a workflow as a technique), but it does not explicitly provide usage context or alternatives. There is no mention of when not to use it or how it differs from related operations like snapshots or imports.

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