collection.set_visibility

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description adds no behavioral context beyond generic risk/maturity labels. It does not explain what changes occur (e.g., visibility flags toggled), whether the operation is reversible, or any side effects. No contradiction, but no added value.

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 short and front-loaded with the command name, but the risk/maturity sentence is boilerplate that does not earn its place. It is concise but not informative.

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 mutation tool with no idempotency and no destructive hint, the description should explain what visibility change is performed and what the boolean parameters control. The output schema exists but the description still fails to provide the minimal context needed to call the tool correctly.

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 only 43%, and the description does not compensate. The 'name', 'render', and 'viewport' parameters are undocumented in the schema and the description gives no hint that 'render' and 'viewport' control visibility channels. The description adds no parameter meaning beyond the raw schema.

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 only restates the command name and adds generic risk/maturity metadata. It does not state what the tool does (e.g., toggles collection visibility in viewport/render) or distinguish it from sibling tools like blender_object_set_visibility or blender_collection_create.

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 on when to use this tool versus alternatives. The only usage-related statement is 'Per-request argument checks and session policy still apply', which is generic harness boilerplate and does not help an agent decide when to invoke this tool.

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