Move a Blender object by absolute location or relative offset, not both, to set its position in the scene.
Move an object. Provide either 'location' for absolute positioning or 'offset' for relative movement, not both.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| offset | No | ||
| location | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full behavioral burden. It never states the coordinate space (world vs. local vs. parent-relative), units, whether the move is undoable, or what happens on an out-of-range value. For a mutation tool with zero annotation coverage this is a significant gap.
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 short sentences, zero waste, with the action front-loaded and the parameter rule immediately after. Ideal size for this tool.
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?
An output schema exists, so return values need not be explained. However, for a 3-parameter transform tool with no annotations and 0% schema coverage, the core ambiguity of the coordinate space is left unaddressed.
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 0%, so the description must compensate, and it does partially by defining 'location' as absolute and 'offset' as relative plus their mutual exclusivity. It says nothing about the coordinate frame, units, or expected vector length for either parameter, leaving real ambiguity.
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?
States a specific verb and resource: 'Move an object.' An agent can immediately tell this is the translation tool and not rotate/scale/duplicate. It does not name any sibling explicitly, but the resource is unambiguous.
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?
Gives explicit parameter-mode guidance: use 'location' for absolute positioning, 'offset' for relative movement, never both. Missing any when-to-use-vs-alternatives guidance (e.g., versus blender_python_exec for complex transforms), but the mode selection rule is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.