streamlabs_load_scene_collection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a state-changing effect ('Switch') but does not disclose potential side effects, error behavior, required permissions, or what happens to the current scene/collection. This leaves the agent with limited information about the tool's runtime behavior.

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 that wastes no words. It states the action, the resource, and the parameter source in a concise manner.

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 one-parameter tool, the description covers purpose and parameter source adequately. However, with no annotations and no output schema, it leaves gaps around return values, error handling, and post-conditions. These would be helpful for an agent to fully understand the tool's behavior.

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 schema only provides the parameter name 'collectionId' with type 'string' and no description. The description compensates by explaining that the parameter is the scene collection id and instructs the agent to retrieve ids via streamlabs_list_scene_collections. This adds meaningful context beyond the raw schema.

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 the specific verb 'Switch' and clearly identifies the resource as 'scene collection', with the method 'by id'. This clearly distinguishes it from sibling tools like streamlabs_get_active_scene_collection (read) or streamlabs_create_scene_collection (create).

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 states when to use the tool: when you want to switch to a different scene collection. It also provides a concrete pointer to streamlabs_list_scene_collections for obtaining valid ids. However, it does not explicitly mention when not to use it or name alternative tools for related tasks.

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