triangulate_mesh

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the conversion of quads/ngons to triangles but does not mention whether the operation is destructive, if it preserves UVs or vertex normals, or any limitations (e.g., performance on high-poly meshes). The description provides only surface-level behavior.

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 sentences followed by a parameter list. The first sentence concisely states the action, the second provides usage context. The parameter list is clearly formatted with values and defaults. No redundant or irrelevant information.

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 simplicity (2 parameters, no output schema, no annotations), the description covers the core purpose and parameter meanings. However, it lacks behavioral details (e.g., what happens to existing triangles, undo support) and does not describe the return value (likely success/failure). It is minimally adequate but not comprehensive.

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 adds essential meaning: 'name: Mesh object name' and 'method: BEAUTY (best quality, default), FIXED, FIXED_ALTERNATE, SHORTEST_DIAGONAL'. It explains the purpose of 'name' and lists the allowed values for 'method'. However, it does not elaborate on what each method does (e.g., fixed vs beauty), which would help an agent choose correctly.

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 tool's action: 'Triangulate all faces of a mesh (convert quads/ngons to triangles).' It also gives a specific use case: 'Useful before export to game engines or 3D printing.' This distinguishes it from sibling tools like subdivide_mesh or separate_mesh by focusing on converting face types.

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 explicit context for when to use the tool: before export to game engines or 3D printing. However, it does not mention when not to use it or suggest alternative tools (e.g., using modifiers for non-destructive triangulation). The guidance is clear but lacks exclusions.

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