blender_mesh_dissolve

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

No annotations are present, so the description carries the full burden. It discloses the core mutating behavior (removing elements) and the key merge-to-fill-gap effect, which is meaningful. However, it omits potential side effects such as UV/topology changes, invalid-index handling, or whether the object must be in edit mode, leaving gaps for a destructive mesh 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?

The description is two sentences, front-loaded with the action and then the distinguishing contrast. It is efficient, scannable, and contains no filler.

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 4-parameter mutation tool with no output schema and no annotations, the description covers the core operation and the delete-vs-dissolve distinction. It omits practical context like prerequisites (edit mode, object type), behavior on invalid indices, and relationships to sibling tools like merge or fill, so it is adequate but not thorough.

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%, with clear descriptions for all four parameters including the mode enum, indices, object_name, and use_face_split. The description adds no parameter-specific meaning beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb ('Remove') with a clear resource ('vertices, edges, or faces') and adds the distinctive behavioral nuance 'preserving surrounding geometry.' The contrast 'Unlike delete, dissolve merges the surrounding geometry to fill the gap' clearly separates it from deletion and communicates its unique function.

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 explicitly contrasts with delete, explaining that dissolve merges surrounding geometry to fill the gap, which gives an agent actionable guidance on when to prefer this tool over deletion. However, it does not mention alternatives like merge or fill, nor provide explicit exclusions, so it is not a complete routing guide.

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