create_collection

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

With no annotations, the description must disclose behavioral traits. It states 'create' (a mutation), but provides no information about side effects, required permissions, effects on existing collections, or return values. The description is minimally honest but insufficiently transparent.

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 very short (4 words), but this is not concise in a useful sense—it omits essential information. It fails to earn its place by adding value beyond the tool name.

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?

Despite having only one parameter and an output schema, the description is completely inadequate. It doesn't explain what creating a collection entails, how it relates to sibling tools, or what the output schema represents. In a complex system like Blender, such minimalism is unacceptable.

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 only parameter 'collection_name' is not described beyond its name in the schema. The description adds no meaning about the format, constraints, or expected values. With 0% schema coverage, this is a critical gap.

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 'Create a new collection' is a tautology that merely restates the tool name. It lacks specificity about what a 'collection' refers to in the Blender context (e.g., object collection vs. data collection) and does not differentiate from sibling tools like 'add_to_collection'.

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 provided on when to use this tool versus alternatives (e.g., 'add_to_collection'), nor are there any prerequisites or context for when creation is appropriate. The description is silent on usage scenarios.

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