outliner-view_layer_create

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, but it only repeats the action of creating. It does not mention side effects, naming constraints, duplicate handling, whether the new layer becomes active, or what happens if creation fails.

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 extremely short and front-loaded with no filler. However, it is under-specified rather than efficiently concise, providing only a literal restatement of the tool's 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?

The tool has one parameter and no output schema, but the description still omits important contextual details about view layers in Blender, such as whether the layer is added to the current scene, whether it must be unique, and how it interacts with outliner visibility tools. The current description is minimally adequate but leaves meaningful gaps for an agent.

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 0%, and the description does not add any meaning to the single 'name' parameter beyond the schema's title 'New view layer name.' The description fails to compensate for missing parameter details such as naming rules, uniqueness, or character restrictions.

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?

Description states a specific verb and resource: 'Create a view layer.' This clearly identifies the operation and differentiates from sibling tools like outliner-view_layer_delete and outliner-collection_create through the 'view layer' resource. However, it does not elaborate on what a view layer is or how it relates to the outliner context.

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 about when to use this tool versus alternatives. There is no mention of prerequisites, such as an existing scene or collection, nor any comparison with related tools like outliner-view_layers or outliner-view_layer_delete.

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