streamlabs_set_scene_item_visibility

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the operation and ID sourcing, without mentioning side effects, error handling, reversibility, or any impact on other scene items. The description adds minimal behavioral insight beyond what the name implies.

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 two sentences, front-loaded with the primary purpose and followed by a helpful usage hint. There is no redundant text, making it highly concise and well-structured.

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 tool with 4 required parameters, no output schema, and no annotations, the description is too sparse. It fails to explain the role of sourceId, the semantic distinction between the IDs, or what happens on success/failure. The active-scene pointer is useful but insufficient for a complete understanding.

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 schema description coverage at 0%, the description must compensate. It explains where to get sceneId and sceneItemId, and 'visible' is implied by 'show or hide', but sourceId is completely unexplained. The relationship between sceneId, sceneItemId, and sourceId is also not clarified, leaving a significant semantic 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 clearly states the tool's action ('Show or hide a scene item') and distinguishes it from sibling scene item operations like transform or scale. It also provides a pointer to obtain the required IDs from streamlabs_get_active_scene, making the purpose unambiguous.

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 explicitly tells the user to get sceneId and sceneItemId from streamlabs_get_active_scene, providing a clear context and prerequisite for using the tool. It does not explicitly mention when not to use it or alternative tools, but the active-scene context and operation purpose implicitly guide usage.

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