blender_sculpt_remesh_voxel

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

With no annotations, the description carries the full burden. It usefully reveals the voxel round-trip mechanism and flags the resource cost of small voxel_size ('more polygons'). But it omits that a remesh rebuilds topology from scratch, typically destroying UV maps, shape keys, and vertex groups, and never states whether the object is modified in place.

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?

Four sentences, each earning its place: purpose, mechanism, use cases, and the key parameter tradeoff. The core verb-object statement is front-loaded, and there is no filler or repetition of schema content.

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?

Covers what, why, when, and the main parameter knob, which is adequate for a simple tool. However, for a destructive mesh operation with zero annotations, it should disclose side effects (loss of UVs/attributes), in-place vs. new-object behavior, and how it differs from blender_ai_mesh_remesh. These gaps are material for agent decision-making.

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 coverage is 100%, so the baseline is 3. The description adds marginal value for voxel_size by restating the detail tradeoff and adding the polygon-count consequence, but smooth and fix_poles receive no context beyond their schema descriptions.

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?

States a specific verb-resource pair ('Apply voxel remesh to create a uniform topology'), explains the mechanism ('Converts the mesh to a voxel representation and back'), and the outcome ('evenly-spaced quads'). The voxel method is clearly named, which distinguishes it from the similarly-purposed sibling blender_ai_mesh_remesh.

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?

Explicitly names three appropriate contexts: cleaning up boolean results, imported meshes, and preparing for sculpting. However, it never names alternatives or states when not to use it, particularly versus the AI-based remesh sibling, so it falls short of full exclusion guidance.

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