Detach objects from their parent hierarchy while preserving world position and rotation.
把对象从父级解绑（取消层级）。keepTransform 保持世界位置/旋转不变。 [English] Unlink objects from their parent. keepTransform keeps world position/rotation.
| Name | Required | Description | Default |
|---|---|---|---|
| objects | No | 对象名称列表；省略则用当前选择。 | Object names; omit for the selection. | |
| keepTransform | No | 保持世界变换，默认是。 | Keep world transform, default true. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, setting the safety profile. The description adds meaningful behavioral context by explaining that keepTransform preserves world position/rotation, which is beyond the schema. It does not contradict annotations, and the added detail clarifies the side effect of the flag.
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 extremely concise, with two short bilingual lines. The key action and parameter effect are front-loaded. Every word earns its place, and there is no filler or redundancy.
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 tool is simple, with no output schema and both parameters fully documented. The description covers the core behavior and the keepTransform flag. While it does not mention edge cases like nested children or undo behavior, the provided information is sufficient for an agent to correctly invoke the tool. The low complexity makes this adequate.
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 both parameters are already documented in the schema. The description reiterates the keepTransform behavior, adding minimal new meaning beyond the schema. It does not introduce any novel parameter information, so the baseline of 3 applies.
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: 'Unlink objects from their parent' and explicitly mentions the keepTransform behavior. It is specific and distinct from siblings like parent_objects (the inverse) and group/ungroup, leaving no ambiguity about what the tool does.
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 states the action but does not provide explicit guidance on when to use this tool versus alternatives like parent_objects or group_objects. It does not mention exclusions or conditions that would route an agent to this tool over others. The usage context is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.