outliner.layer_collection_set

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

With no annotations, the description bears full responsibility for behavioral disclosure. It does not explain side effects, idempotency, return values, or whether it overrides existing restrictions. The mention of 'restrictions' is vague.

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, but it is too short and under-specified for a tool with 6 parameters. It lacks necessary details, making it less effective despite its brevity.

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 6 parameters, no output schema, no annotations, and numerous sibling tools, the description fails to explain how restrictions interact with each other, prerequisites, or the tool's role in the outliner domain. It is incomplete.

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%, yet the description only generically refers to 'restrictions' without detailing individual parameters. The schema titles provide some meaning (e.g., 'Exclude collection from this view layer'), but the description adds no additional semantics beyond the titles.

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 states 'Set view-layer collection restrictions for one collection', which uses a specific verb ('Set') and identifies the resource ('view-layer collection restrictions'). It distinguishes from siblings like outliner.collection_visibility_set by focusing on multiple restrictions (exclude, holdout, etc.), but could be more explicit about the exact parameters.

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 such as outliner.view_layers or outliner.collection_visibility_set. There is no mention of prerequisites or contexts where this tool is appropriate.

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