add_blueprint_do_once_node

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the node's runtime behavior, lists all pins, and describes the return structure, giving the agent a clear picture of what the operation produces. It could go further by noting side effects like graph mutation or prerequisites, but the core behavior is well covered.

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 well-structured and front-loaded with the primary action, followed by concise behavior, pin, parameter, return, and example sections. Every sentence adds value without unnecessary verbosity.

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 covers the node's behavior, pins, parameters, return values, and includes an example call, which is strong for a 3-parameter tool with an output schema. Minor gaps remain around prerequisites such as the blueprint already existing or graph resolution semantics, but the definition is largely complete.

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 0%, yet the description compensates fully by documenting every parameter: blueprint_name, graph_name, and node_position, including defaults and types. This provides meaning far beyond the input 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 clearly states the verb and resource: 'Add a DoOnce macro node to a Blueprint graph.' It explains what the node does, which helps the agent understand the tool's purpose. However, it does not explicitly differentiate this from the very similar sibling tool add_do_once_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?

The behavior description, 'only fires the Completed output once until Reset is triggered,' implies the tool should be used when a one-shot execution pattern is needed. No explicit when-not-to-use guidance or alternatives are provided, so usage context is implied rather than stated.

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