blender_mesh_tris_to_quads

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

With no annotations, the description carries the burden of behavior disclosure. It does explain the pairing criteria—angle and UV matching—and implies an in-place topology modification. However, it doesn't mention side effects, reversibility, or what happens when no valid quad pairs are found.

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, tight sentence that front-loads the operation and outcome before giving the pairing criteria. No wasted words or redundant restatement of the tool name.

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 focused mesh operation with a fully documented input schema, the description is largely complete: it explains what the tool does and the algorithm it uses. It stops short of noting in-place mutation or operation limitations, but no major information needed to invoke it correctly is missing.

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 100%, so the parameters are already well documented. The description adds minimal semantic value by referencing angle and UV matching, which loosely maps to angle_limit and compare_uvs, but does not meaningfully supplement the schema.

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 resource—'Convert triangles to quads'—and states the intended outcome: cleaner quad topology. This clearly differentiates the tool from the many sibling mesh operations like dissolve, merge, or remesh.

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?

It gives a clear use context: cleaning up triangulated meshes to achieve quad topology. It doesn't explicitly name alternatives or exclusion cases, but the purpose is specific enough that an agent can infer when this tool applies.

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