outliner.collection_visibility_set

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

No annotations are provided, so the description carries the full burden. It indicates a mutation action but does not disclose behavioral traits like reversibility, effect on child collections, or authorization requirements. The agent is left with minimal understanding of 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?

A single sentence effectively conveys the tool's purpose. No redundant information, and it is front-loaded with the key action. Excellent conciseness.

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 simple boolean setter tool with no output schema, the description is adequate but lacks safety context (e.g., non-destructive nature) and clarification of collection existence. Given the sibling tools, it sufficiently identifies the target domain (collections) but could be more complete for an agent with no prior knowledge.

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?

With 0% schema description coverage, the description must compensate. It provides a general mapping of 'viewport', 'render', and 'selectability' to the corresponding boolean parameters, but does not explain each parameter's effect or the required 'collection' parameter beyond its title. Some added value, but insufficient detail.

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 clearly states the tool sets collection-level restrictions for viewport, render, and selectability, matching the boolean parameters. It distinguishes from siblings like outliner.visibility_set by specifying 'collection-level'. However, it could be more explicit about the boolean nature of the settings.

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.visibility_set for objects or other outliner tools. The description lacks context for proper tool selection.

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