blender_collection_move

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the basic move action and optional removal, but does not disclose whether the target collection must already exist, how multiple current memberships are handled, or any side effects beyond collection membership.

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 deliver the core action and the key optional behavior with no filler. The main verb and resource appear first, making the description easy to scan.

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 mutation tool, the schema plus description are enough to make a basic call. However, with no annotations or output schema, it would benefit from clarifying target-collection existence requirements and the distinction from instancing.

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 the schema already documents all three parameters. The description adds little beyond restating that objects are moved and may be removed from current collections, which the schema already covers in more detail.

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 the specific verb 'Move' with a clear resource ('objects') and destination ('target collection'), and notes optional removal from current collections. It is clear on its own, though it does not explicitly differentiate itself from the sibling blender_collection_instance.

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?

There is no guidance on when to use this tool versus alternatives such as blender_collection_instance, nor any prerequisites or exclusions. The optional removal behavior hints at a use case, but the tool does not state when moving is preferred to instancing/linking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.