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

No annotations are provided, so the description must carry the full behavioral burden. It implies an additive mutation but does not disclose side effects, permission requirements, whether the node is persisted immediately, what happens to existing workflow structure, or what the tool returns.

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 front-loaded with the core action and then supplies the valid node type list. It contains no filler, and every element is useful for correct invocation.

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?

The schema fully documents the five parameters, and the description adds the complete node type enumeration. However, with no annotations and no output schema, it omits behavioral details such as side effects, prerequisites, and return value, leaving meaningful gaps for a mutation tool with a nested config 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 the baseline is 3. The description adds substantial value by enumerating all valid nodeType values, going beyond the schema's brief examples and helping the agent avoid invalid node types.

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 a specific verb and resource: "Add a node to a workflow." This clearly distinguishes it from delete_node, update_node, and connect_nodes by action, but it does not explicitly name or contrast those siblings.

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 no guidance on when to use add_node versus alternatives such as update_node or connect_nodes, nor does it state prerequisites like needing an existing workflow or workspace. Usage is only implied by the verb "add."

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