outliner-layer_collection_set

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

With no annotations, the description carries the full burden of disclosure, but it only says 'Set... restrictions.' It does not state whether this mutates existing settings, whether boolean flags overwrite or merge with current values, what happens if the view_layer or collection does not exist, or any side effects.

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?

One concise sentence, front-loaded with the verb and resource, and free of filler. It is structurally clean, though the brevity comes at the cost of missing useful context.

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?

This tool has six parameters, two required, no annotations, and no output schema, yet the description is only a single clause. It lacks prerequisites, behavior on existing settings, validity constraints, and any indication of return values or errors. The description is not complete enough for an agent to invoke this correctly in varied situations.

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 adds almost no parameter meaning. 'Restrictions' vaguely hints at boolean toggles like exclude, holdout, viewport, and indirect_only, but domain-specific terms such as 'holdout' and 'indirect_only' remain completely unexplained.

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 uses a specific verb ('Set') and identifies the resource ('view-layer collection restrictions') for one collection. It clearly indicates the operation's scope, though it does not explicitly distinguish itself from sibling tools like outliner-collection_visibility_set or outliner-view_layers.

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 given about when to use this tool versus alternatives such as outliner-collection_visibility_set, outliner-view-layers, or outliner-view_layer_create. The intended usage is only implied by the name and description, with no exclusions or alternative recommendations.

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