outliner-view_layers

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

No annotations are provided, so the description carries the full burden. 'List' clearly implies a read-only operation, but the description does not elaborate on any special behavior, such as whether a particular view layer must be active or what the output structure looks like. It is adequate but minimal for a list 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 a single concise sentence, front-loaded with the verb 'List' and object. No filler or repetition. It earns its place fully.

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 zero-parameter list tool with no output schema, the description effectively communicates the output (view layers and restriction trees) and scope. It lacks an explanation of the exact structure of 'layer-collection restriction trees', which could confuse agents unfamiliar with Blender, but overall it is sufficient for a simple query tool.

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 tool has zero parameters and an empty schema, so the parameter baseline of 4 applies. The description adds no parameter information because there are none to describe. The schema already fully covers the parameter space.

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 uses a specific verb 'List' with a clear resource 'view layers' and further specifies 'their layer-collection restriction trees', which distinguishes it from sibling tools like outliner-tree or outliner-describe.

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?

Usage is implied by the name and description: it is for listing view layers and their restriction trees. However, there is no explicit guidance on when to use this versus alternatives, nor any exclusions or context about when this tool is preferable to outliner-tree or outliner-find.

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