dissolve_edges

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

The description discloses that edges are dissolved, faces merged, and overall shape preserved. However, it lacks details about destructive nature, edge cases (e.g., non-manifold geometry), or prerequisites. With no annotations, the description carries the full burden but is only moderately transparent.

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 three sentences plus parameter/returns lines, efficiently stating purpose and expected input/output. It is front-loaded with the core action. Could be slightly more structured (e.g., separating args and returns clearly).

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 moderate complexity and no annotations, the description adequately covers the basic operation and parameter but does not explain behavior with multiple edges, effects on UVs or normals, or compare with sibling dissolve tools. The output schema exists but is not described.

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%, so the description must compensate. While it lists the parameter 'object_name' and says 'Name of the mesh object', it adds no meaning beyond the schema's type and title. The parameter is simple, but the description provides no extra context like valid format or usage notes.

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 dissolves all edges and merges adjacent faces, with a specific verb and resource. It distinguishes itself from sibling tools like dissolve_faces and dissolve_verts by focusing on edges.

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 guidance on when to use this tool versus alternatives (e.g., dissolve_faces, bevel_edges). The description implies usage for simplifying topology by removing edge loops, but does not provide exclusion criteria or comparisons.

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