boolean_operation

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

The description discloses that apply=True applies the modifier and removes the cutter, but does not mention destructive nature, mesh requirements, or behavior when apply=False. Given no annotations, the transparency is moderate.

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 very concise, consisting of three short sentences. It is front-loaded with the core purpose, but could be better structured with bullet points for operations.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description provides a basic understanding but lacks details on return values, prerequisites, and the full workflow. It is minimally sufficient.

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?

With 0% schema description coverage, the description explains the 'operation' and 'apply' parameters, but 'target' and 'cutter' are only implied as 'two mesh objects'. This adds some meaning but not complete coverage for all four parameters.

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 tool performs a boolean operation on mesh objects, lists the three operation types, and explains the apply behavior. It is specific and unambiguous, distinguishing it from sibling tools like 'boolean_cleanup'.

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 'bmesh_operation' or 'boolean_cleanup'. The description implies usage for boolean operations but does not specify prerequisites or exclusions.

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