mesh_curvature_gaussian_mean_analyzer

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

With no annotations, the description must carry the full behavioral burden. It mentions computation and feature highlighting, but does not state whether the tool is read-only, how it handles the input mesh, or what side effects (beyond the cost note) might occur. The price is disclosed, but operational safety (e.g., no mutation) is absent.

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?

A single, front-loaded sentence states the primary action and outcome efficiently. The price note is parenthetical and useful without adding fluff. Every word serves a purpose.

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?

Despite the clear purpose, the description fails to specify the input mesh format expected in payload or the output structure of the computed curvatures. With no output schema, the agent lacks key invocation details, such as how to pass the 3D mesh and what the result looks like.

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 100%, with both payload and paymentSignature already documented. The tool description adds no meaning beyond the schema, so the 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 clearly states the tool's function with a specific verb ('Computes'), a precise resource ('per-vertex principal, Gaussian, and Mean surface curvatures'), and the target subject ('3D meshes'). It distinctively differentiates from mesh decimation, packing, and Boolean CSG siblings by naming the exact geometric measurements.

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 description implies usage for mesh curvature analysis through its wording buys dtype, but it does not explicitly state when to use this tool versus alternatives like mesh_decimate_quadric_simplifier or pointcloud_icp_rigid_registration. No exclusions or conditional guidance is provided.

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