rhino_align_mesh_vertices

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

There are no annotations, so the description must disclose behavioral traits, but it only says vertices are aligned without explaining what 'align' actually does to the mesh, whether the operation is destructive, or what side effects occur. A mutation tool with no mention of selection requirements, reversibility, or output behavior leaves too much unspecified.

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 compact, front-loaded with the main behavior, and uses a readable Args block. The inclusion of the controller argument, which does not appear in the input schema, adds minor noise, but overall the structure is efficient and not padded.

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 omits essential context about how the target mesh is specified, whether the operation applies to a selection, and what happens to the mesh after alignment. With no annotations and only a tolerance parameter in the schema, an agent cannot confidently invoke this tool without additional implicit knowledge.

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 description defines tolerance as 'distance tolerance for vertex alignment,' which adds real meaning beyond the bare schema property. Although the schema has 0% description coverage, the description compensates fully for the single tolerance parameter; the 'controller' parameter mentioned in the description is not present in the schema, which causes slight confusion.

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 a specific action ('align') on a specific resource ('mesh vertices') with a defined criterion ('within tolerance'). This distinguishes it from the generic rhino_align sibling, though it does not explicitly contrast it with closely related mesh-repair tools like rhino_weld_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 no guidance on when to use this tool instead of alternatives, nor does it state any prerequisites such as which mesh is selected or how the target mesh is identified. The large sibling list includes similar mesh modification tools, but the description offers no routing information.

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