add_while_loop_node

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

No annotations are provided, so the description must carry the burden of explaining side effects of this mutation, but it only describes the node's runtime behavior. It does not say what happens in the blueprint graph, whether connections are made, or what effects occur beyond adding the node.

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 compact and well-organized with behavior, args, KB link, and example. Each section earns its place, though the Args block slightly repeats parameter names already in the schema.

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 description is minimally viable: it explains the node, documents both parameters at a basic level, includes an example, and points to KB fundamentals. It still lacks prerequisites, graph placement context, and coordinate format, which an agent needs to invoke it confidently.

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?

With 0% schema description coverage, the description compensates only partially: it labels blueprint_name and node_position, marks node_position as optional, and gives an example path. It does not explain the format or units for node_position coordinates.

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?

Description opens with 'Add a While Loop node', a specific verb and resource, and then clarifies the node's runtime semantics ('Executes Loop Body while condition is true, then fires Completed'). This is enough to distinguish it from the many sibling loop-node tools such as add_blueprint_for_loop_node.

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 guidance is given for when to choose this tool over alternative loop nodes, nor are any preconditions or exclusions mentioned. The KB pointer is a reference, not a usage rule.

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