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 of behavioral disclosure. It only states that selected mesh elements are dissolved, without mentioning destructive side effects, how selection is interpreted, what limited mode does, or whether boundaries/vertices are affected.

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 short sentence with no filler, which is concise. However, it is under-specified for a tool with five parameters and multiple dissolve modes, so it is not appropriately sized for the complexity.

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?

With no annotations, no output schema, and 0% schema description coverage, the one-sentence description leaves the agent without information about mode semantics, defaults, object targeting, or side effects. This is inadequate for a 5-parameter mesh operation.

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%, and the description does not mention any of the five parameters (type, object, use_verts, angle_limit, use_dissolve_boundaries). The schema titles and defaults are self-descriptive, but the description adds no meaning to help an agent understand parameter semantics.

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 the specific verb 'Dissolve' with the resource 'selected mesh elements,' clearly identifying a mesh editing operation. It does not explicitly distinguish it from sibling tools like mesh-delete or mesh-merge, but the operation name is specific enough to convey the core purpose.

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 guidance is provided about when to use dissolve versus alternatives such as mesh-delete, mesh-merge, or mesh-remove_doubles. There is also no mention of selection prerequisites or how the 'type' mode affects usage.

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