mesh-quads_to_tris

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

With no annotations provided, the description carries the full disclosure burden. It states the core mutation but doesn't mention that the operation is destructive, that it operates on the active/selected object, or how the different triangulation methods affect results. This is minimal transparency for a mesh-editing tool.

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 a single front-loaded sentence with no filler words, which is excellent conciseness. However, it is so brief that it omits essential operational context, making it slightly under-specified rather than optimally structured.

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 three parameters, two of which are enum-based, and no annotations or output schema, the description is incomplete. It explains the basic operation but fails to mention object targeting or the meaning/selection of triangulation methods, leaving an agent without enough context to invoke the tool confidently.

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 0% and the description adds no meaning for object, ngon_method, or quad_method. The enum values (BEAUTY, CLIP, FIXED, etc.) are left unexplained, and the description doesn't even hint that these parameters exist.

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 uses a specific verb and target ('Convert selected faces to triangles') that precisely identifies the operation and scope. It clearly distinguishes from siblings like mesh-tris_to_quads, mesh-subdivide, or mesh-fill.

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 implies you need selected faces but provides no explicit guidance on when to use this tool versus alternatives such as mesh-subdivide, mesh-tris_to_quads, or mesh-fill. It also doesn't mention prerequisites like being in edit mode or requiring a mesh object.

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