merge_by_distance

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

The annotations already signal destructive behavior, but the description adds no additional behavioral context. It doesn't mention that vertices are permanently merged, that topology changes, or that the operation is applied to a specific object. The description's statement about removing duplicates is more purpose than behavioral detail.

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 extremely short and front-loaded, but it is under-specified. While it earns credit for being concise, it omits critical information, making it insufficient rather than appropriately concise.

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 that this is a destructive mesh operation with two parameters and an output schema, the description is severely incomplete. It provides no instruction on how to invoke it, what the object_name means, what distance does, or what to expect in the output. This is inadequate for an agent to use the tool correctly.

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%, and the description does not explain the parameters. The 'distance' parameter's meaning (threshold for merging vertices) is not described, and 'object_name' is not mentioned at all. The description provides no value beyond the raw schema field names.

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 removes duplicate vertices, which is a specific and recognizable operation. However, it does not explicitly differentiate from similar mesh cleanup tools like clean_mesh that might also remove duplicates, so it lacks full sibling differentiation.

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?

No usage context is provided. The description does not explain when to use this tool versus alternatives like clean_mesh or validate_geometry, nor does it mention prerequisites or scenarios where merging by distance is appropriate.

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