analyze_mesh_geometry

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

The description lists the metrics computed and supported file types, but with no annotations provided, it carries full burden. It does not explicitly state that the tool is read-only (no side effects) or discuss potential pitfalls (e.g., large file handling, time complexity). This is adequate but leaves some behavioral aspects implicit.

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 paragraph with a clear docstring format, front-loaded with the main purpose. It includes parameter and return descriptions with no wasted words. Every sentence adds value.

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?

The tool has 1 parameter, no output schema, and no annotations. The description lists the return type and key metrics, providing a solid overview. However, it could be more precise about the return dict structure and error handling, but given the tool's moderate complexity, it is sufficiently complete.

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 has 1 parameter (file_path) with 0% description coverage. The description adds 'Path to .stl, .obj, or .glb file,' specifying the file formats, which is meaningful beyond the schema's type constraint.

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 it performs deep geometric and printability analysis of a 3D mesh, listing specific computed metrics (volume, surface area, center of mass, etc.) and supported file formats (.stl, .obj, .glb). This distinguishes it from sibling tools like analyze_model_geometry or analyze_printability.

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 provides explicit usage context: 'Use this after generating a model to understand its geometry and identify printability issues before sending to the slicer.' However, it does not mention when to avoid using this tool or compare it directly to alternatives like diagnose_mesh or analyze_model_geometry.

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