rhino_triangulate_mesh

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

With no annotations provided, the description must carry the behavioral disclosure burden. It does convey that the tool operates on selected meshes and transforms quad faces, which implies in-place modification. However, it does not disclose whether the operation is destructive, whether undo is available, or what happens if no meshes are selected.

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 one focused sentence with no filler. The core action is front-loaded, and the Args line adds minimal but acceptable context. Every word serves the definition.

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?

For a zero-parameter mesh conversion tool with an output schema, the description is mostly complete. It identifies the target objects (selected meshes) and the operation. The main gap is that it does not state whether the conversion replaces the original meshes or creates new geometry.

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 input schema has zero parameters, so there is little to document. The description's mention of 'controller: RhinoController instance' is not reflected in the schema but is boilerplate rather than a user-facing parameter. Baseline 4 applies for zero-parameter tools.

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 and resource: 'Convert all quad faces in selected meshes to triangles.' It clearly differentiates this tool from siblings like rhino_quadrangulate_mesh and other mesh editing tools by defining the exact transformation performed.

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 clearly implies when to use the tool: when selected meshes contain quad faces that should be converted to triangles. However, it does not explicitly mention alternatives, exclusions, or when not to use it, so it stops short of full guidance.

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