add_do_n_node

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

No annotations are provided, so the description carries the full burden. It discloses the execution count and blocking behavior, which is core to the node's function. It does not mention side effects like graph mutation or return values, but for a node-add operation this is acceptable.

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-structured: a one-line purpose, a behavioral note, a clean Args list, a KB reference, and an example. Every element earns its place without redundancy.

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 tool is simple (3 params, 1 required) and the description covers all params and behavior. It also provides a KB link and example. It could add a note about reset semantics, but the core information is present.

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?

The schema has no parameter descriptions (0% coverage), so the description compensates fully. It explains blueprint_name as the target, n with default and meaning, and node_position as optional graph coordinates. The example demonstrates a real call, making parameter usage unambiguous.

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 verb 'Add' and the resource 'Do N node', with a concise behavioral summary ('executes a specified number of times'). It distinguishes itself from sibling loop nodes by naming the specific 'Do N' behavior, and includes an example to anchor usage.

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 explains the blocking behavior after N executions and the reset condition, which is a key usage constraint. However, it does not explicitly contrast this node with alternatives like Do Once or For Loop, leaving the agent to infer when this node is the right choice. The behavior note is useful but not a full usage guide.

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