comfyui_add_node

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

With no annotations, the description must carry the behavioral disclosure burden. It adds only a hint that verification is optional, but fails to state that this is a write operation that modifies the workflow, or how expected_revision and verify_node_type affect behavior. This is insufficient for a mutation tool.

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, concise sentence that front-loads the primary action and adds a secondary optional behavior. No redundant information 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 7 parameters, no annotation coverage, and only a minimal description, the tool lacks sufficient context for an agent to understand workflow modification semantics, return values, or the meaning of 'managed workflow.' The output schema exists but does not compensate for missing operational guidance.

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%, and the description provides no explanation of parameters such as class_type, inputs, node_id, or expected_revision. The agent receives no help understanding how to populate these fields, making the tool difficult to use correctly.

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: adding a node to a managed workflow, with an optional live verification against ComfyUI. This distinguishes it from sibling tools like remove_node and connect_nodes by focusing on the creation action.

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?

No explicit guidance on when to use this tool versus alternatives. The phrase 'optionally checking it against the live ComfyUI' hints at a validation use case, but there is no mention of when to skip verification or scenarios where other tools (e.g., set_input) would be more appropriate.

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