mesh_operation

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

The annotations already declare destructiveHint=true, so the description does not need to restate that these are destructive operations. However, it does not disclose additional behavioral context such as in-place mutation of the mesh data block, effect on existing modifiers, or failure/return behavior. The operation-specific parameter hints add a little context beyond the annotation.

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 compact single sentence with no filler, listing operations and their params in a scannable format. It is dense but every element contributes useful information; slight formatting polish could improve readability.

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 multi-operation tool with no enums in the schema and no output schema, the description covers the operation catalog and parameter keys, which is the minimum needed to invoke it. It omits return values, error behavior, and object_name context, making it adequate but not fully complete.

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?

With 0% schema description coverage, the description is the only source of parameter meaning. It documents the allowed operation strings and their associated params keys (cuts, offset, segments, angle_limit, distance), which is essential. It leaves object_name implicit and does not specify types or defaults for the params values, so it is not fully complete.

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 clear action ('bmesh operation on a mesh') and enumerates the specific operations it can perform (subdivide, bevel, triangulate, decimate, merge_by_distance, recalc_normals), which tells an agent what the tool does. It stops short of explicitly distinguishing itself from sibling tools like add_modifier, but the direct-mesh-operation framing provides enough clarity.

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 statement about when to use this tool versus alternatives such as add_modifier or validate_mesh. The operation list implies some use cases, but no when-to-use/when-not-to-use guidance or prerequisites are given.

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