boolean_cleanup

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

With no annotations, description must disclose behavior. It details the cleanup pipeline (EXACT solver, dissolve degenerate, etc.) but does not reveal whether the tool is destructive, modifies in place, or any side effects on the mesh.

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?

Extremely concise: a single line for purpose, then bulleted parameter list. No filler. Informative yet efficient.

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?

With an output schema present, return values are covered. The description fully documents all four parameters and their behavior. Could mention side effects like whether it modifies the mesh in-place, but overall complete for the tool's complexity.

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 description must compensate. It does so by clearly explaining each parameter: mesh_name as target, cutter_name with special empty behavior, operation with enums and default, auto_cleanup with function. Adds significant meaning beyond schema.

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?

Clearly describes a boolean operation with an automatic cleanup pipeline, distinguishing it from the simpler sibling tool 'boolean_operation'. The verb 'operation' combined with 'cleanup' makes the purpose specific.

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?

Implies usage for boolean operations needing cleanup, but does not explicitly state when to prefer this over sister tools or alternative approaches. No exclusions or context provided.

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