compare_mesh_versions

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

With no annotations provided, the description carries full burden. It lists computed metrics and return format, indicating a read-only operation, but does not disclose permissions, file format assumptions, or error handling. The transparency is adequate but not exhaustive.

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 concise at roughly 80 words, front-loads the purpose, and organizes metrics and parameters in a clear, scannable manner. No unnecessary words.

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?

Given no output schema, the description explains return values (dict with metrics and flag). It covers purpose, usage, parameters, and output. Missing are error conditions or file format restrictions, but for the complexity level, it is fairly 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?

The description adds meaning beyond the schema by labeling file_a as 'reference (original) mesh' and file_b as 'modified mesh'. Schema coverage is 0% in structured form, so the description compensates well. However, it leaves out file format details and validation.

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 verb 'compare', resource 'mesh files', and expected output 'geometric differences'. It is specific enough to distinguish from sibling tools like analyze_mesh_geometry or diff_design_versions.

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 explicitly says 'Useful for verifying that a repair, rescale, or regeneration actually improved the model', giving context on when to use. It does not mention when not to use or provide alternative tools, but the guidance is clear.

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