sdf_mesh_marching_cubes_extractor

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

No annotations are provided, so the description carries the full burden. It discloses the cost (0.045 USDC on Base L2) and the algorithm, but does not mention any side effects, input/output formats, or potential failure modes. It does not state whether the operation is read-only or mutating. The cost is a useful behavioral note, but more detail (e.g., on payment requirements, output structure) would be expected for a paid tool.

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 a single, information-dense sentence with the core purpose front-loaded and the cost appended at the end. No wasted words; it is concise and well-structured.

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?

Without an output schema, the description should explain what the output looks like (e.g., mesh format, file type). It only says 'extracts smooth watertight polygon meshes', which is vague about the actual return value. It also does not specify the input representation of the SDF field or clarify the paymentSignature's role (though it mentions cost). For a paid, complex tool, this is insufficient.

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% as both parameters have descriptions. The description adds no additional parameter details beyond the schema. Since the schema already documents both parameters adequately, a baseline of 3 is appropriate.

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 uses a specific verb ('Extracts') and identifies the resource ('smooth watertight polygon meshes from volumetric 3D Signed Distance Fields'), and mentions the algorithmic approach ('adaptive dual contouring and Marching Cubes'). This clearly differentiates it from siblings like mesh_watertight_manifold_auditor (which audits watertightness) and signed_distance_field_sdf_baker (which bakes SDFs). The purpose is unambiguous.

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?

There is no explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description does not mention any conditions, exclusions, or preferred alternatives. An agent might not know when to choose this over related mesh or SDF tools without additional reasoning.

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