streamlabs_get_active_scene

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

With no annotations, the description carries the burden. The verb 'Get' clearly indicates a read-only operation, and 'including its scene items' specifies the return content. This is sufficient for a simple getter, though it does not explicitly state side-effect-free behavior or potential edge cases (e.g., no active scene error).

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 directly states purpose and return content. Every word earns its place; there is 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?

Given zero parameters and no output schema, the description fully explains what the tool returns ('the currently active scene, including its scene items'). No additional context is necessary for this simple getter.

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?

There are zero parameters, and the schema is empty. The description correctly implies no inputs are needed. Per the rubric, 0 parameters warrants a baseline of 4 since there is no parameter ambiguity to resolve.

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 tool's function: 'Get the currently active scene, including its scene items.' The verb 'Get' and resource 'currently active scene' are specific and distinguish this from sibling tools like list_scenes (list all) and get_scene (get by specific identifier).

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 usage when you need the active scene, but it does not explicitly contrast with sibling tools such as streamlabs_get_scene or streamlabs_list_scenes. There is no clear context for when to choose this over alternatives, though the name itself strongly suggests the appropriate scenario.

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