plasticity_deform_bodies_between_faces

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

Annotations only declare it is a non-read-only, non-destructive, closed-world mutation. The description adds real beyond-annotation context: source bodies and both reference-face bodies are preserved, the operation creates independent copies, and deformation intentionally changes shape and dimensions. This tells an agent what is and isn't consumed by the operation.

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?

Three dense sentences that front-load the core operation before preservation semantics and parameter notes. Little waste, though the second and third sentences pack multiple ideas without breaking them apart.

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 an 11-parameter, no-output-schema, nested-object mutation tool, the description covers purpose, preservation behavior, and a subset of parameter meaning. It leaves revision (likely a concurrency token), intent, and the ids/sourceFace/targetFace structure unexplained, which an agent would want for correct invocation.

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 0% across 11 parameters, so the description must compensate. It clarifies that scaleU/scaleV/scaleNormal and the orientation flags (flipUV, mirror, flipNormal) are dimensionless mapping controls, which is genuinely useful. However, ids, sourceFace, targetFace, revision, and intent get no explanation.

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+resource: create independent Solid/Sheet copies by mapping all faces from a source face onto a target face. This distinguishes it from the near-sibling plasticity_deform_curves_between_faces (bodies vs curves). It stops short of explicitly naming the alternative, but the scope is unambiguous.

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 is implied (creating deformed copies while preserving originals) but there is no explicit when-to-use, when-not-to-use, or alternative routing. The caveat to inspect resulting geometry is a warning rather than selection guidance.

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