collection.create

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

Annotations are all false (not read-only, not idempotent, not destructive), but the description does not clarify what side effects occur when creating a collection, such as adding it to the scene or respecting a parent. The mention of 'Risk: standard; maturity: L3' and generic session policy adds no behavioral detail beyond the annotation fields.

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 short but not effectively concise; it is under-specified defense. It repeats the command name and adds boilerplate without substantive content. It does not front-load the purpose or key usage facts.

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?

Given the tool has six parameters, an output schema, and many sibling collection-related commands, this description does not provide enough context for an agent to know how to invoke it properly. It lacks operation semantics, parameter guidance, and relationships to sibling tools, leaving critical gaps.

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 only 50% (name, parent, and _expectedSceneRevision lack descriptions). The description provides no explanation of what 'name' or 'parent' mean or how they affect the operation. With six parameters alerting an agent, this is insufficient compensation for the incomplete schema.

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 only restates the command name 'collection.create' and adds generic harness metadata. It never explicitly says that this tool creates a collection in Blender, so an agent cannot derive what action is performed. This is a tautology of the title/name.

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 like blender_collection_move_object or blender_collection_set_visibility. The only operational notes ('Per-request argument checks and session policy still apply') are generic harness requirements, not tool-specific usage direction.

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