blender_collection_instance

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

No annotations are provided, so the description carries the full behavioral burden. It states the action but does not disclose side effects, such as whether calling it multiple times accumulates instances, whether existing instances are replaced, whether the source collection remains unchanged, or what coordinate system and units apply. These are material gaps for a mutation tool.

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, focused, front-loaded sentence. The verb and resource appear immediately, and the examples add useful context without fluff. Every part earns its place.

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?

With no annotations and no output schema, the description provides only basic purpose and use-case context. It is serviceable for a simple call but lacks behavioral guarantees, prerequisites, and explicit routing guidance among the many similar sibling tools.

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 parameters. The description adds contextual motivation for use but does not clarify array shapes, defaults, or relationships between locations, rotations, and scales beyond what the schema already states.

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 a specific verb and resource: 'Place collection instances at specific locations.' It also gives concrete examples of when this is useful, which helps distinguish it from broad operations. However, it does not explicitly differentiate it from related sibling tools like blender_object_duplicate or blender_geonode_scatter_instances.

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 phrase 'efficient placement of repeated complex objects' implies a clear use case and gives context. But there is no explicit guidance on when not to use this tool or what alternatives to prefer, especially given the many related placement/duplication/scatter tools in the sibling list.

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