add_set_difference_node

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

Without annotations, the description carries the full burden. It does state the core mutation ('Add a Set DIFFERENCE node') and clarifies what the node computes, but it does not disclose side effects, behavior when the node already exists, whether compilation is needed, or what the operation returns beyond what an output schema might cover.

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 readable, with a clear statement, args list, knowledge-base pointer, and example. The only real flaw is redundancy: the set-difference definition appears twice in nearly the same words.

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 simple two-parameter node-adding tool with an output schema present, the description provides enough context to call it successfully: target blueprint, position format, an example, and a KB reference. It does not spell out all failure modes or mutation side effects, but the low complexity keeps this acceptable.

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%, so the description must compensate. It provides useful meaning for both parameters: blueprint_name is 'Blueprint to add the node to' and node_position is '[X, Y] graph position.' It also gives a concrete invocation example. Minor gaps remain around optionality and coordinate-space details.

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 identifies the verb ('Add') and resource ('Set DIFFERENCE node'), then defines the operation with the example 'elements in first set but not in second.' This distinguishes it from sibling set-node tools like add_set_union_node and add_set_intersection_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 use case is implied through the set-difference semantics, but the description never explicitly says when to choose this instead of a union, intersection, or contains node. It provides no exclusions or alternative routing, so the agent must infer the choice from the mathematical definition.

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