create_node

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

With no annotations, the description carries the full behavioral burden but only implies a mutation. It does not disclose what the create operation requires (auth/permissions), whether it returns the created node or its ID, how autoConnect/targetNodeId mutate the graph, or any side effects on the workflow.

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?

A single front-loaded sentence with the verb and resource first. It is appropriately short, though 'with advanced configuration options' is vague padding that does not earn its place.

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 mutation tool with a nested required object, no annotations, no output schema, and no explanation of the auto-connection parameters, the description is insufficient. An agent cannot tell what happens on creation, what is required beyond the two required keys, or what is returned.

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% and the nested node object is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema; it never mentions workflowId, position, autoConnect, or targetNodeId.

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?

States a specific verb (Create), resource (node), and scope (in a workflow), so the agent knows this is a node-creation tool. It does not distinguish itself from the sibling update_node or delete_node, and 'advanced configuration options' is filler rather than a differentiator.

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?

There is no guidance on when to use this tool versus update_node or create_connection, no mention of prerequisites like an existing workflow or required node type/version, and no conditions or exclusions. The description assumes the reader already knows the context.

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