Set Skin Weights

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

Annotations are minimal, so the description must carry behavioral disclosure. It adds the batch limit (1000 entries) and optional normalization, which are helpful. However, it does not describe side effects, required permissions, or error behavior, leaving gaps 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?

Two sentences: first sentence states the action and optional feature, second adds a key constraint. No unnecessary words. Well-structured and front-loaded.

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 description covers the core purpose and a constraint, but misses context like prerequisite skin binding, or explanation of the output schema (which exists). For a tool with 3 parameters and a mutation action, additional context about the intended state changes would improve completeness.

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 baseline is 3. The description adds value by explaining the normalization option context and the batch size limit for the weights parameter, which is not fully captured in the schema alone.

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 verb 'Set' and the resource 'per-vertex skin weights', and also includes the scope of up to 1000 entries per call. It is distinct from sibling tools like 'skin.weights.get' which reads weights.

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 description implies when to use (to set weights) but does not explicitly state when not to use or compare to alternatives. It mentions the batch limit, which provides some usage guidance, but lacks exclusions or context vs. other skin weight tools.

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