Merge Vertices

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

The description implies a mutation (merge), consistent with readOnlyHint=false. It adds the distance threshold detail, but does not disclose other behaviors like effect on topology, selected vs. all vertices, or reversibility. Annotations already indicate non-destructive nature, so the description adds a modest amount of context.

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, well-structured sentence with no extraneous words. It is front-loaded with the core purpose, making it efficient for an agent to parse.

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 simple interface and presence of an output schema, the description is minimally adequate. However, it does not clarify the scope of merging (e.g., which vertex is kept, effect on mesh structure), which would be helpful for a modeling operation.

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 coverage is 100%, so the schema already describes all parameters. The description mentions 'distance threshold' which maps to the threshold parameter, but does not add meaning beyond the schema's description. Baseline score 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 action (merge) and the resource (vertices on a mesh), with a condition (distance threshold). It is distinct from sibling tools like modeling.bevel or modeling.bridge, which perform different 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, such as when cleaning up geometry or selecting specific vertices. No exclusions or alternative tools are mentioned.

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