weld_mesh_edges

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful scope and a return shape (triangle_count, vertex_count, welded), but does not explain what gets destroyed, whether the operation mutates in place, or error/edge-case behavior. With annotations carrying the safety burden, this is an adequate 3.

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 two tight lines: a front-loaded purpose sentence followed by the return shape. There is no waste, and the most important information comes first.

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?

The description covers what the tool does and the return values, which is helpful given there is no output schema. However, for a destructive mesh-editing operation with three parameters, it omits prerequisites, failure modes, and guidance relative to sibling mesh-repair tools, leaving meaningful gaps.

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 100%, so all three parameters are documented in the input schema. The description does not add semantic detail beyond the schema, other than echoing parameter names in the return object, so the baseline 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 states a specific verb (Weld), resource (coincident open boundary edges), and target (a DynamicMeshActor's dynamic mesh), making the operation unambiguous. It does not, however, name or distinguish itself from related mesh tools such as get_mesh_open_border_loops, get_num_open_border_edges, or repair_mesh_self_intersections, so sibling differentiation is absent.

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, no prerequisites such as needing existing open border edges, and no exclusions. It only says what the tool does, leaving context entirely to inference.

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