Move Blender objects into a target collection, removing them from their current collections. Optionally create the collection if it does not exist.
Move objects into a collection, unlinking them from their current ones.
| Name | Required | Description | Default |
|---|---|---|---|
| names | Yes | ||
| create | No | Create the collection if missing | |
| collection | Yes | Target collection name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It does reveal the key side effect — unlinking objects from their current collections — but does not mention reversibility, failure modes, or what happens to collection membership when the target already contains the object.
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, front-loaded sentence with no redundant wording. Every part contributes to explaining the operation: the action, the target, and the side effect.
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?
For a simple three-parameter operation without an output schema, the description plus schema is arguably enough to attempt a call. However, with no annotations and no usage guidance, the agent still lacks clarity on edge cases like missing objects, duplicate membership, or whether collection creation is attempted by default.
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 coverage is 67%, with 'create' and 'collection' already described in the schema. The description adds no parameter-level meaning, and the 'names' parameter is only documented by title and type, leaving an agent to infer that these are object names.
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: 'Move objects into a collection'. The additional phrase 'unlinking them from their current ones' differentiates this from copying/adding behavior and from sibling tools like create_collection or list_collections.
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?
No guidance is given about when to use this tool versus alternatives, nor any exclusions or prerequisites. An agent must infer that this is for re-organizing existing objects between collections without help from the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.