merge_vertices

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

With no annotations, the description must disclose behavioral traits. It explains the core merging behavior and practical context, but does not mention potential side effects (e.g., irreversibility, object modification, or any prerequisites). A higher score would require more explicit details about the operation's impact.

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 concise: three sentences plus a parameter list. The first sentence immediately states the purpose, followed by a helpful analogy and use cases. Every sentence adds value with no redundancy.

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 tool's moderate complexity and lack of output schema, the description adequately covers the operation, parameters, and context. It could mention the outcome or return value, but the functionality is well-explained for agent use.

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 schema has 0% description coverage, so the description compensates by explaining both parameters: 'Mesh object name' for name, and 'Maximum distance between vertices to merge (default 0.001)' for distance. This adds essential meaning beyond the schema's titles.

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 (weld) vertices' and specifies the resource and condition: 'within a distance threshold'. It uses the Blender analogy ('Merge by Distance') and provides use cases, effectively distinguishing it from sibling tools like join_objects or separate_mesh.

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 gives explicit use cases ('cleaning up imported meshes or fixing seams after boolean operations'), which helps the agent understand when to use it. However, it does not state when not to use it or compare to alternatives, though for a single-purpose tool this is acceptable.

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