obs_set_source_visible

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

With no annotations, the description must convey the tool's effect, and 'show or hide' does that simply. However, it does not disclose additional traits such as reversibility, persistence of the visibility change, or behavior if the sceneItemId is invalid—though for this simple setter the core behavior is clear.

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 well-worded sentence with an example, front-loading the action immediately. There is no redundant content or padding.

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 three-parameter mutation with fully described schema, the description provides sufficient context: what the tool does, the targeted entity, and examples. No output schema exists, but none is expected; the only minor gap is not explicitly clarifying that this action does not create or remove sources.

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?

The input schema already covers all three parameters with 100% coverage, including the meaning of the `visible` boolean and the provenance of `scene_item_id`. The description adds no extra semantic value beyond what is in the schema, so the baseline of 3 applies.

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 uses a specific verb ('show or hide') with a clear resource ('one source inside a scene') and provides relatable examples ('drop the overlay, hide a camera'). This clearly distinguishes it from sibling tools like obs_scene_item_remove, obs_scene_item_lock, or obs_set_source_transform.

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?

The description gives clear context about the operation but does not explicitly state when to prefer it over alternatives such as removing, duplicating, or locking a scene item. The schema's reference to getting the ID from obs_list_sources_in_scene implies workflow, but there is no explicit exclusion of other scene-item tools.

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