set_collection_visibility

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

No annotations are provided, and the description gives no behavioral details—such as whether this toggles visibility, what the hide_render and hide_viewport defaults mean, side effects on the scene, or return values. The agent has no idea what operation is performed.

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?

While the description is very short, this is not conciseness—it is absence of content. It simply restates the tool name as a label, which is under-specification rather than efficient communication.

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 the tool has three parameters (one required) and an output schema, a minimal description is insufficient. An agent has no guidance on correct invocation, parameter meaning, or expected behavior, making this completely inadequate for safe use.

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 coverage is 0%, and the description adds nothing about the parameters. The schema itself only lists names without types or descriptions, so parameters remain completely opaque. The description fails to compensate for this gap.

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 repeats the tool name with a prefix, 'Blender Studio Pro MCP: set_collection_visibility', and provides no verb, resource, or effect. It is a tautology that offers no insight into what the tool actually does.

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?

There is no guidance on when to use this tool versus the many collection-related siblings like list_collections, create_collection_hierarchy, delete_collection, or move_to_collection. The agent cannot infer appropriate usage or exclusions.

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