Copy Skin Weights

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

The description does not disclose whether the operation overwrites existing target weights, whether it is reversible, or any side effects. Annotations indicate destructiveHint=false, but copying weights typically modifies the target's skinCluster, which may be considered destructive. The description provides no clarification.

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 sentence that conveys the core action and method efficiently. No unnecessary words, but could benefit from a brief usage hint.

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 that an output schema exists (not shown), the description adequately covers the high-level operation. However, it lacks details about return values, error conditions, and prerequisites beyond 'must have a skinCluster' (which is already in the schema).

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% with detailed parameter descriptions. The description adds minimal semantic value by mentioning 'surface and influence association methods', which paraphrases the parameter names. Baseline 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 clearly states the action ('copy skin weights'), the resource ('from one mesh to another'), and the method ('using surface and influence association methods'). It is specific and actionable, but does not differentiate from sibling tools like skin.weights.set.

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?

No guidance is provided on when to use this tool versus alternatives such as skin.weights.set, skin.bind, or skin.influences. The description does not mention prerequisites, limitations, or typical use cases.

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