streamlabs_get_scene

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

No annotations are provided, so the description must carry the behavioral transparency burden. It discloses that the tool returns the scene 'with its items', which is useful. However, it does not mention error behavior if the scene id doesn't exist, return format, or any side effects (though as a getter, side effects are minimal). The description is adequate but lacks depth.

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 all essential information 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?

The tool is simple (one parameter, no output schema), so the description covers the basics: what it does and the key input. However, it lacks details about return structure, error handling, or any prerequisites. Given no output schema and no annotations, the description is sufficient but not rich enough to fully anticipate behavior in edge cases.

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%, so the description must compensate. It does so by explaining the parameter's role: 'by scene id' clarifies that sceneId identifies the scene to retrieve. This directly adds meaning beyond the raw schema, which only lists sceneId as a required string. For a single parameter, this is decent compensation.

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 a specific scene (with its items) by scene id.' It uses a specific verb ('Get') and a specific resource ('a specific scene'), and distinguishes it from siblings like streamlabs_list_scenes (which lists all) and streamlabs_get_active_scene (which gets the active one).

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 context of use: when you have a scene id and need that particular scene and its items. It is clear that this is for fetching a specific scene, not for listing or switching. However, it does not explicitly name alternatives or exclusion conditions, but the context is evident.

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