comfy_add_node

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

The description says 'workflow dictionary to modify' and 'Add a node', implying mutation, while the annotations declare readOnlyHint: true. This is a direct contradiction, making the tool's behavior ambiguous. No additional behavioral details (e.g., in-place vs. return new copy, uniqueness of node_id) are given.

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 brief and front-loaded with the primary action, then lists parameters in a readable format. It avoids fluff, though the 'Args:' labeling could be trimmed for even conciseness.

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 simple add-node operation, the description covers the essential behavior and all parameters. However, the contradiction with annotations and lack of usage guidance make it less complete than it could be. The presence of an output schema reduces the need to describe return values.

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 0%, so the description fully compensates by explaining each parameter: workflow (dictionary to modify), node_id (string, with example '8'), class_type (ComfyUI class type), and inputs (optional). This adds meaningful context 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 states 'Add a node to a workflow' with a clear verb+resource. It distinguishes from sibling operations like connect_nodes or build_workflow by focusing on the single action of adding a node with explicit parameters.

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 usage context is provided. The description does not indicate when to use this tool instead of comfy_set_widget_value, comfy_connect_nodes, or comfy_build_workflow. It lacks any exclusions or prerequisite conditions.

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