dissolve_faces

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

Describes the core behavior: faces are dissolved and merged, keeping mesh structure intact. With no annotations provided, it carries the full burden and does so clearly. It doesn't mention destructiveness or undo capabilities, but the description is sufficient for understanding the operation.

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?

Three sentences plus argument and return list. No filler. Purpose is front-loaded. Every sentence adds value.

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 single parameter and the presence of an output schema (though not shown), the description is quite complete. Could mention whether it acts on all faces or only selected, but 'all faces' is clear. Return is noted as confirmation dict.

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?

With 0% schema description coverage, the tool description compensates by explicitly listing the argument and explaining it is the name of the mesh object. This adds meaning beyond the schema's type and title.

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?

Clearly states that it dissolves all faces and merges them into surrounding geometry, distinguishing it from siblings like dissolve_edges and dissolve_verts. Also explicitly compares it to deleting faces, emphasizing the benefit of no holes.

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?

Provides context on when to use (to remove faces without holes) and mentions an alternative (deleting faces). However, it lacks explicit when-not-to-use scenarios or other alternatives, which would further guide selection.

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