mesh.remove_doubles

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'Merge duplicate vertices' without disclosing whether it modifies normals, UVs, or other attributes, if it operates on selected vertices or whole mesh, or if it is destructive. The threshold parameter is mentioned but its effect is unclear.

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?

While the description is very short, it is under-specified. It lacks necessary details about usage and parameters. True conciseness would retain essential information without waste, but here critical context is missing, making it insufficient.

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 the complexity of a mesh operation that modifies geometry, with no annotations, no output schema, and no parameter descriptions, the description is completely inadequate. It does not explain threshold behavior, scope of operation, or results, leaving the agent blind to important details.

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 0%, meaning no parameter descriptions in the schema. The tool description adds no information about the two parameters (object and threshold). The agent must infer their purpose from names alone, which is insufficient for correct invocation.

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 'Merge duplicate vertices' clearly states the primary action (merge) and resource (vertices). It is specific and distinguishes it from siblings like mesh.merge which likely merges objects or other elements, and mesh.dissolve which removes geometry. However, it does not explicitly differentiate from potential ambiguity with other vertex operations.

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 no guidance on when to use this tool versus alternatives. It does not indicate prerequisites (e.g., vertex selection), nor when not to use it (e.g., when merging entire meshes). No context is given for its appropriate use case.

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