blender_physics_cloth_add

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states that cloth simulation is added, but does not disclose what happens if the object already has a cloth modifier, whether the operation is additive or replaces existing simulation settings, or whether any destructive side effects occur. This is a notable gap for a mutation tool.

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 single, compact sentence that front-loads the core action and then efficiently enumerates the supported capabilities. Every phrase contributes useful information without redundancy.

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?

Given the moderate complexity of the tool and the complete parameter schema, the description is minimally viable. It conveys the essential operation and supported options, but it does not mention workflow context such as whether simulation playback or baking is required afterward, or how this tool fits with blender_physics_simulate.

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 mentions categories like material presets, vertex group pinning, collision objects, and wind, which loosely map to parameters, but it does not add meaning beyond what the schema already provides in detail.

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 clearly states the action ('Add') and the resource ('cloth simulation to a mesh object'), specifying the exact purpose. It is immediately distinguishable from sibling physics tools like soft_body_add and rigid_body_add because it explicitly names cloth simulation.

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?

Usage context is implied: an agent would infer to use this tool when adding cloth simulation to a mesh. However, there is no explicit guidance about when to prefer this over soft_body_add or rigid_body_add, nor any mention of prerequisites like needing a mesh object to already exist.

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