blender_collection_visibility

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

With no annotations, the description carries the full behavioral disclosure burden, but it only names the affected properties and view layer. It does not explain whether optional flags are left unchanged when omitted, what happens if the collection is not found, or whether 'toggle' means flipping current state versus setting the given values.

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 concise sentence that front-loads the action and resource, with no filler or repetition. Every word contributes.

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 full parameter schema and the 'current view layer' qualifier make the tool mostly usable. However, the missing clarification around optional-boolean behavior and failure handling means it is not entirely complete for an agent invoking it safely.

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 100%: each boolean and collection_name has a clear descriptive meaning. The tool description merely restates the property names without adding new parameter-level detail, so the schema baseline holds.

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 names a specific action—toggle—and a specific resource, collection, and lists the exact properties affected: visibility, renderability, and selectability. This clearly differentiates it from collection_create/list/move siblings, which have different purposes.

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?

It gives a useful context qualifier, 'in the current view layer,' which helps an agent infer when it applies. However, it does not explicitly state when to use this tool versus alternatives or mention any prerequisites or exclusions, leaving usage mostly implied.

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