boolean_union

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

With no annotations, the description must disclose behavioral traits, but it only says 'Union OpenSCAD objects.' It does not indicate whether the operation is destructive, what side effects occur, or any required permissions. The agent gains no insight beyond the tool's name.

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 only three words, which is under-specification rather than conciseness. It provides no additional context, sentences, or structure to help the agent.

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?

Despite having an output schema, the description gives no indication of the return value or behavior. It lacks essential context for a Boolean operation tool and is inadequate for an agent to understand input, output, or usage.

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. The only parameter, object_ids, is not explained at all. The description does not clarify what these IDs represent (e.g., IDs of existing OpenSCAD objects), their format, or where they come from.

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 states the operation (Union) and resource (OpenSCAD objects), but lacks scope or specificity. It distinguishes from siblings like boolean_difference and boolean_intersection, but does not clarify what 'Union' means in the 3D modeling context.

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 is provided on when to use this tool versus alternatives such as boolean_difference or boolean_intersection. The description does not mention prerequisites or conditions for use.

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