streamlabs_remove_scene_item

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 explicitly discloses the key side effect: the scene item is removed but the underlying source remains. This is critical for an operation that might be mistaken for deletion. It does not mention error cases or reversibility, but for this straightforward tool, the main behavior is well covered.

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 exactly two sentences. The first sentence states the main action, and the second adds a crucial clarification. Every word earns its place, with no fluff or redundancy.

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?

The tool is simple with no output schema, and the description covers the core purpose and the key nuance about not deleting the source. It is mostly complete, though it lacks explicit parameter guidance (e.g., why sourceId is needed when sceneItemId is present).

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 0%, and the description does not explain what sceneId, sceneItemId, or sourceId mean beyond their names. It mentions 'scene' and 'source instance' but does not clarify how the three identifiers relate, making it hard for an agent to know which ID goes where.

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 action (remove a scene item) and the resource (scene item from a scene), and explicitly distinguishes it from deleting the underlying source. This is a specific verb+resource definition that sets it apart from siblings like streamlabs_remove_source.

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 implies the appropriate scenario by clarifying that the underlying source is not deleted, which indirectly distinguishes it from streamlabs_remove_source. However, it does not explicitly say when to use this tool versus alternatives, such as 'use streamlabs_remove_source to delete the source entirely.'

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