add_blueprint_variable_set_node

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

No annotations are provided, so the description carries the burden. It clearly implies mutation ('Add') and discloses the return dict, but it does not warn about preconditions (e.g., whether the blueprint must be compiled/loaded), save-side effects, or potential failures if the variable doesn't exist. This is acceptable but not exhaustive.

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 docstring is well organized with Args, Returns, KB, and Example sections. Every section adds value—especially the example and KB pointer—and there is no redundant filler.

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?

Covers all parameters, provides defaults, a usage example, and a knowledge base reference. It does not detail the exact structure of the returned dict beyond keys, but that is minimal for an agent operating in this domain. Overall, it adequately enables correct invocation.

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 0% description coverage, and the description compensates by explaining each parameter in the Args section, including defaults and optionality. While target_class's 'same resolution as native bridge' is cryptic, the rest clarify the schema meaning well.

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 the specific operation ('Add a 'Set Variable' node') and the target resource ('for a Blueprint variable'). The verb and object are unambiguous, and the node type is clearly distinguished from sibling tools like add_blueprint_variable_get_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 explicit 'when to use' or when-not-to-use guidance. The example shows a call but does not contrast this with similar sibling tools like add_set_variable_node or add_blueprint_variable_get_node. The KB link is a reference but not usage guidance.

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