blender_mesh_bisect

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

With no annotations, the description carries the full behavioral burden and does disclose the key side effects: it can clear geometry on either side and fill the cut plane. It also clarifies the geometric behavior of an infinite cutting plane. It does not state whether the original mesh is modified in place or what the default result is when clear/fill flags are false, but the core mutation semantics are clear.

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?

Two concise sentences with no filler. The first sentence states the mechanism immediately, and the second summarizes optional behavior and provides a concrete use case. Every word earns its place.

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?

The description covers the operation, the geometry, and the optional behaviors, which is adequate for selecting the tool. However, with no output schema and no annotations, it doesn't describe the return value, whether the mesh is destructively modified, or the default result when no clear/fill options are set. These are meaningful gaps for a mutation tool, though not severe.

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%, so the parameters are already well documented. The description reinforces the meaning of plane_point, plane_normal, clear_inner/clear_outer, and fill, but adds no new constraints, formats, or edge-case details beyond the schema, so the baseline score of 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?

The description specifies the exact operation ('Cut mesh'), the geometric method ('infinite plane defined by a point and normal'), and optional outcomes (clear sides, fill cut). This is a specific verb-plus-resource statement that clearly distinguishes bisect from sibling mesh operations like bevel, extrude, or loop_cut, even without naming alternatives.

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 phrase 'Perfect for splitting vehicles into sections' provides a concrete use case, so an agent can infer this is for slicing a mesh along a plane. However, there are no explicit when-to-use/when-not-to-use conditions or named alternatives such as mesh_split or knife_project, so the guidance is implied rather than directive.

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