Modify bone properties in an armature: set head, tail, roll, deform, parent, connect, or inherit scale. Clear parent by passing an empty string.
修改骨骼（parent 传空字符串即清除父级）。
| Name | Required | Description | Default |
|---|---|---|---|
| bone | Yes | ||
| head | No | ||
| roll | No | ||
| tail | No | ||
| deform | No | ||
| parent | No | ||
| connect | No | ||
| armature | Yes | ||
| inherit_scale | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the parent-clearing behavior but omits side effects, error conditions, return values, or whether the bone must already exist.
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 concise sentence with no redundant information. The parent-clearing note is directly relevant and efficiently conveyed.
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?
With nine parameters, no output schema, and no annotations, this minimal description is far from sufficient for an agent to understand the full behavior, parameter meaning, return value, or edge cases.
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 has no per-parameter descriptions, and the tool description only clarifies 'parent' with the empty-string behavior. The other eight parameters (head, tail, roll, deform, connect, etc.) remain unexplained.
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 uses a specific verb '修改' (modify) with a clear resource '骨骼' (bone), and the parent-empty-string note helps distinguish this from add/remove/list bone tools. However, it is somewhat generic and does not explicitly state that it targets existing bones.
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 only usage hint is that passing an empty string to parent clears the parent. There is no explicit guidance on when to use set_bone versus add_bone, remove_bone, or list_bones, nor any mention of prerequisites like selecting an armature.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.