mesh_boolean_csg_exact

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

With no annotations, the description must disclose behavior itself; it reveals exact arbitrary-precision math, coplanar-face handling that avoids crashes, and a 0.050 USDC Base L2 cost. However, it does not disclose input/output format, side effects, failure modes, or precision limits.

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 front-loaded sentence with dense, non-redundant information; every clause advances the value, including the cost. No filler.

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 complex geometry tool with no output schema and no annotations, the description omits the minimal payload contract (mesh format, operand count, operation selection) and return semantics. An agent would have to guess the JSON structure to invoke it correctly.

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?

Both parameters are described in the schema (100% coverage), so the baseline applies; the description adds domain intent but no payload syntax. It never explains how to encode the two meshes and an operation into the required payload string, nor what paymentSignature must contain beyond the schema's generic text.

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?

Description names the exact operation: arbitrary-precision CSG mesh boolean operations with Union, Difference, and Intersection, and highlights coplanar-facet robustness. This clearly separates it from geometric siblings like optimize_3d_mesh, mesh_decimate_quadric_simplifier, and mesh_convex_hull_quickhull, none of which perform CSG booleans.

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 explicit when-to-use or when-not-to-use guidance is provided, and no alternative tool is referenced. The use case must be inferred from the operation names; the description never says which sibling to prefer for approximating vs. exact booleans.

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