dissolve_verts

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

With no annotations, the description carries the full behavioral burden. It discloses the key effect ('Removes vertices while preserving surrounding geometry'), which is useful, but says nothing about whether this is a destructive edit, mode requirements, or reversibility. Partial disclosure for a mutation 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?

Front-loaded with the core action, then structured Args and Returns sections. No wasted sentences, though the Args/Resturns scaffolding is slightly verbose for a two-parameter tool.

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?

An output schema exists, so the description needn't explain returns, and parameters are covered. But for a mesh-mutating tool with zero annotations, it omits operational context (edit vs object mode, destructiveness) that an agent would need to invoke it safely.

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, and it does: it defines object_name and fully explains the selection enum ('ALL' vs 'CURRENT'), its default, and the prerequisite select_* workflow. This adds meaning well beyond the bare enum in 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 states a specific verb and resource ('Dissolve all vertices') and adds a clarifying mechanism ('merging connected edges and faces'), which separates it from generic dissolve tools. It does not explicitly name the sibling alternatives like dissolve_edges or dissolve_faces, but the vertex focus makes the target unambiguous.

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 actionable guidance for the selection parameter ('Use the select_* tools to choose first'), which is a genuine usage hint. However, it never states when to prefer this over merge_vertices or the other dissolve_* tools, so the routing decision is left implied rather than explicit.

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