obs_scene_item_remove

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

With no annotations, the description carries full burden and excels: it explains that only the placement is removed, the source remains intact in other scenes, settings/filters persist until the last placement is removed, and there is no undo over the websocket. This is rich, non-obvious behavioral disclosure.

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?

Three dense paragraphs, each earning its place: the action, the placement-vs-source distinction with a concrete example, and the irreversibility warning with an alternative. Slightly verbose but well-structured and front-loaded with the core action.

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 two-parameter tool with no output schema, the description fully covers the side-effect model, the last-reference behavior, and the lack of undo. There are no meaningful gaps regarding what the tool does or what the agent should consider before invoking it.

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 describes both parameters at 100% coverage, with sceneItemId referencing obs_list_sources_in_scene and noting scene-unique scope. The description adds no additional parameter-level detail, so the baseline of 3 for high schema coverage is appropriate.

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 opens with 'Remove one scene item from its scene,' a specific verb+resource statement. It further distinguishes the tool from source deletion and from obs_set_source_visible by clarifying it removes the placement, not the underlying input.

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?

Explicitly provides when-not-to-use guidance: 'If the goal is just to get something off screen, obs_set_source_visible is reversible and this is not.' It also implies the tool is for permanent placement removal with no undo.

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