streamlabs_clear_scene

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

No annotations are provided, so the description carries the full burden. It states the main effect (removing all items) but does not disclose whether the sources are deleted or just unlinked, whether the action is reversible, or any side effects. For a destructive operation, this is a notable 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, front-loaded sentence with no unnecessary words. It conveys the action, target, and outcome efficiently.

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 tool with one parameter, the description covers the core action but leaves ambiguities (e.g., whether sources are destroyed or just removed) and does not mention return value or failure behavior. Given the lack of annotations and output schema, more detail would be expected, but the tool's simplicity keeps it from being severely inadequate.

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 single parameter sceneId is not described in the schema (0% schema description coverage). The description implies that sceneId identifies the scene to clear, which adds minimal context, but it does not specify the format, source, or any constraints beyond the schema's type string. This partially compensates but remains thin.

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 ('Remove') and resource ('all items (sources) from a scene'), with an outcome ('leaving it empty'). This clearly distinguishes it from sibling tools like streamlabs_remove_scene (delete the entire scene) or streamlabs_remove_scene_item (remove a single item).

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 explicit guidance on when to use this tool versus alternatives. While the action is clear, the description does not mention exclusions (e.g., not for removing a single item) or alternatives such as streamlabs_remove_scene_item. Usage context is only implied by the name and description.

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