blender_collection_create

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

With no annotations present, the description carries the full burden of behavioral disclosure. It merely states that a collection is created and that collections organize objects. It does not mention potential behaviors such as what happens if the name already exists, whether the collection is created under the Scene Collection by default, or what the tool returns/does not return. This is a minimal behavioral description for a creation operation.

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 two short sentences with no redundant wording. The first sentence front-loads the core action, and the second adds relevant conceptual context about collections. Every word earns its place; there is no filler or unnecessary detail.

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 create operation, the description is mostly adequate, and the schema covers all parameters. However, with no output schema and no behavioral notes about default parent behavior or name conflicts, an agent still has to infer some execution details. It is not incomplete enough to be dangerous, but it could be richer given that the description is the only source of behavioral context.

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 input schema fully documents all three parameters (name, parent, color_tag) with descriptions and enum values, giving 100% schema description coverage. The tool description does not add parameter-level detail beyond the schema. Because the schema already carries the meaning, a baseline score of 3 is appropriate.

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 action and resource: 'Create a new collection,' which is specific and unambiguous. It conveys the essential purpose of collections in the Blender scene hierarchy. However, it does not explicitly differentiate this tool from sibling tools like blender_collection_list, blender_collection_move, or blender_collection_instance, relying mostly on the verb 'create' to distinguish it.

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 provides no explicit guidance on when to use this tool versus alternatives. It explains what collections do conceptually but does not say 'use this when you need a new collection,' nor does it mention any conditions or exclusions. There is no reference to siblings such as blender_collection_list or blender_collection_move that would help an agent choose correctly.

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