blender_mesh_shrinkwrap

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys the core mutating behavior (vertices get repositioned onto another surface) but does not clarify whether the deformation is a permanent direct edit or a modifier-based operation, whether it is reversible, or what happens with invalid targets. For a geometry-mutating tool with zero annotation coverage, this is a notable but non-fatal gap.

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?

A single front-loaded sentence that leads with the core verb phrase, followed by two compact illustrative examples. Every word earns its place; there is no fluff, repetition, or irrelevant detail.

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 tool is moderately complex (5 params, 1 enum, 2 required) and the schema covers all parameters, so the essential calling contract is documented. However, with no annotations and no output schema, the description should disclose side effects, prerequisites (e.g., target must be a mesh object), and whether the edit is destructive. The partial use-case guidance does not fully close that gap.

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 baseline is 3. The description reinforces the meaning of object_name and target_object ('another object's surface') but adds no meaning for mode, offset, or vertex_indices beyond what the schema already provides. The description does not compensate beyond the schema.

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 and resource: 'Snap vertices to another object's surface.' This clearly identifies the operation and the involved objects (vertices being snapped, a target surface). The concrete examples ('conform details to body panels, project geometry onto curved surfaces') further clarify intent and distinguish it from sibling mesh editing tools like extrude, bevel, or inset.

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 examples 'conform details to body panels, project geometry onto curved surfaces' provide clear context for when this tool is appropriate. However, it does not explicitly name alternatives or state when not to use it (e.g., it doesn't mention that permanent geometry edits differ from adding a non-destructive modifier via blender_modifier_add).

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