obs-set-scene-item-enabled

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('show or hide') but lacks critical details: whether this requires specific permissions, if changes are immediate or reversible, potential side effects (e.g., affecting overlays or recordings), or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.

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's mutation nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, return values, or error handling. For a tool that modifies scene state in a production environment like OBS, more context is needed to use it safely and effectively.

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%, with each parameter clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., it doesn't explain how to obtain sceneItemId or validate sceneName). Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Show or hide a scene item' clearly states the verb ('show or hide') and resource ('scene item'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'obs-set-source-filter-enabled' or 'obs-remove-scene-item', but the specific focus on scene item visibility is reasonably distinct within the OBS context.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing scene item), exclusions, or comparisons to similar tools like 'obs-get-scene-items' for checking current state or 'obs-remove-scene-item' for deletion. Usage context is implied but not stated.

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