Reposition a modifier on a Blender object by specifying a new index or moving it up, down, to the top, or to the bottom of the modifier stack.
调整修改器顺序：给 index，或 direction UP/DOWN/TOP/BOTTOM。
| Name | Required | Description | Default |
|---|---|---|---|
| index | No | ||
| object | Yes | ||
| modifier | Yes | ||
| direction | 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, and the description does not disclose side effects, whether the operation is destructive, or any permissions required. As a mutation tool, this omission is significant.
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 clear sentence with no unnecessary words. It efficiently conveys the core functionality and the two primary input options.
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, but the description does not clarify whether index and direction are mutually exclusive or how they interact, nor does it mention any return values or error conditions. This leaves some ambiguity for an agent.
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?
The description explains the meaning of 'index' and 'direction' (UP/DOWN/TOP/BOTTOM) but leaves 'object' and 'modifier' undefined. Since these are required parameters, the coverage is incomplete.
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 tool's purpose: adjusting modifier order. It specifies two methods (index or direction), making it distinct from other modifier tools like add_modifier or remove_modifier.
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 the tool (when reordering modifiers) but does not explicitly contrast it with alternatives or mention conditions that would make it preferable over other modifier operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.