limited_dissolve

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

With no annotations, the description carries the full burden of disclosing behavior. It states the core action ('dissolve') which implies removal of geometry, but it does not disclose side effects such as whether the operation is destructive, whether it affects UVs or materials, or whether it is reversible. No warnings about angle threshold limits or unexpected results are given.

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 short and front-loaded with the main purpose in the first sentence. The Args section is compact and directly maps to the schema. It contains no filler, though the parameter descriptions are minimal.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It does not explain what 'dissolve' means in a mesh topology context, how the angle threshold affects the result, or what the tool returns (if anything). Given the complexity of a geometry operation, more context is needed for an agent to call it safely and correctly.

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 compensates by identifying both parameters: 'object_name: Target object' and 'angle_limit: Angle threshold in radians.' However, it does not explain what the angle limit actually measures (e.g., angle between face normals) or provide any context about acceptable or typical values beyond the schema's default.

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 ('Dissolve') and a resource ('geometry') plus the controlling criterion ('angle threshold'). It is not a tautology and is clearly distinct from sibling tools like smooth_vertices or merge_vertices. However, it does not specify whether geometry refers to mesh faces, edges, or vertices, which leaves slight ambiguity.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention whether it is for reducing mesh complexity, cleaning up geometry, or suggest when it should be preferred over similar mesh-editing tools. No exclusions or alternative references are provided.

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