rig_skin_add_bone

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description adds little beyond restating that a bone is added. It does not disclose behavior such as whether the operation replaces existing bones, requires a skin modifier, or has permanent effects beyond the annotation hints.

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 short and to the point, with both Chinese and English versions. The core purpose is front-loaded, though the bilingual duplication is redundant for an agent that only needs one clear expression.

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 and schema cover the basic operation and parameters, but important context is missing: whether the target object must already have a Skin modifier, how multiple objects are handled, and what the weighted mode actually does. For a destructive tool, this is adequate but leaves meaningful gaps.

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 all three parameters are already documented in the schema. The description adds minimal additional meaning about the rigid mode, which closely parallels the existing 'rigid' parameter description, so it does not significantly exceed the baseline.

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: 'Add a bone to the object's Skin modifier,' with an optional rigid/weighted mode. It is clear and unambiguous, though it does not explicitly distinguish itself from sibling tools like rig_skin_add or rig_skin_remove_bone.

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?

There is no guidance about when to use this tool versus alternatives such as rig_skin_add, rig_skin_auto_weight, or rig_skin_remove_bone. It does not mention prerequisites like requiring an existing Skin modifier, nor does it state what happens if no Skin modifier is present.

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