mesh_watertight_manifold_auditor

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

With no annotations provided, the description carries the burden of explaining behavior. It does disclose the inspection scope and cost, and 'audits' implies a non-mutating operation, but it does not state whether it returns a pass/fail verdict, a detailed report, or how failures are represented. This leaves some behavioral ambiguity.

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?

One dense sentence front-loads the action and audit scope, followed by a short cost parenthetical that is relevant to a paid tool. There is 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?

There is no output schema, so the absence of any description of return behavior is a real gap. The generic payload parameter also lacks guidance on which mesh representation (OBJ, GLTF, etc.) is expected, leaving an agent uncertain how to construct a valid call.

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 coverage is 100%, so both payload and paymentSignature are described at least generically in the schema. The description adds no detail about the expected geometry format inside the JSON payload, so it does not improve on the schema baseline.

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 uses a specific verb ('Audits') with a clear resource (3D geometry) and enumerates concrete defect categories, making its function obvious. It also names the intended stage ('before simulation or 3D fabrication'), which distinguishes it from sibling tools like optimize_3d_mesh that modify geometry rather than inspect it.

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?

The phrase 'before simulation or 3D fabrication' gives a clear contextual trigger for when to run the audit. It does not explicitly name alternatives or exclusions, but the inspection-vs-repair distinction is strongly implied by the sibling set.

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