boolean_operation

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

No annotations exist, so the description must disclose side effects. It does not state whether the original nodes are deleted or replaced, whether the operation is destructive, or describe the result node. The mention of 'order matters for SUBTRACT' is helpful but insufficient for a mutation tool.

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?

Single sentence, no wasted words, front-loaded with purpose. Achieves maximum clarity with minimum text.

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 tool that modifies geometry, the description lacks essential context: what happens to the input nodes, what the result is, and any reversibility. Given the lack of output schema, the description should provide this context.

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 100%, so baseline is 3. The description adds the parent constraint, which complements the schema but does not significantly enhance understanding beyond what the schema already provides.

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 explicitly states 'Perform a boolean operation (union, subtract, intersect, exclude) on two or more nodes', using specific verbs and resource (nodes). It differentiates from siblings like group_nodes by specifying boolean operations rather than grouping, and includes a constraint (same parent).

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 on when to use this tool vs alternatives (e.g., group_nodes, flatten_node). It does not provide context for when boolean operations are appropriate or when to expect different behavior. The constraint 'All nodes must share the same parent' is a prerequisite but not a usage guideline.

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