rhino_repair_mesh

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

Description adds behavioral detail: lists specific repairs and notes it is an 'attempt', implying possible incompleteness or failure. No contradiction with destructive annotation; the destructive hint already covers modification, but the description provides useful nuance about expected repair scope.

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?

Single sentence with no fluff. Key details (specific repairs and optional fill_holes) are front-loaded, and the sentence structure is efficient.

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 simple two-parameter tool with an output schema and annotations, the description is largely sufficient. It covers purpose and parameters adequately. It does not explicitly state whether the mesh is modified in place or returned as a new mesh, but the destructive annotation implies modification.

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 descriptions are tautological (e.g., 'Mesh GUID to repair') and coverage is 0%, meaning the schema provides no meaningful parameter info. The description mentions fill_holes but doesn't add meaningful parameter behavior beyond the schema's own minimal description, nor does it explain guid requirements or edge cases.

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?

Clear verb 'repair' with specific resource 'mesh'. Lists common issues (degenerate faces, duplicate vertices, unified normals, fill holes), making it obvious what it does. Distinct from rhino_check_mesh which is diagnostic only.

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?

No explicit when-to-use or alternatives mentioned. The purpose implies usage for meshes with these issues, but no guidance on when not to use or how it compares to other mesh tools like rhino_cap_planar_holes or rhino_check_mesh.

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