streamlabs_list_scenes

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

With no annotations, the description carries the full burden. It clearly implies a read-only operation ('List all scenes') but does not disclose return format, ordering, pagination, or whether scenes include sources. This is minimal but not misleading.

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, focused sentence with no filler. It front-loads the action and object, making it immediately scannable.

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 list operation with no parameters and no output schema, the description is sufficiently complete. It specifies the scope ('current scene collection') and the action ('list all scenes'). However, it could mention the expected return type (e.g., array of scenes) to further guide the agent, so not a perfect 5.

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 tool has zero parameters, and the schema is empty. The description does not need to explain parameters. Per the rubric, 0 params receives a baseline of 4, and there is nothing to add beyond the empty 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 a specific verb ('List') and resource ('scenes'), clearly indicating it retrieves all scenes in the current scene collection. It distinguishes itself from siblings like 'streamlabs_get_scene' (specific scene) and 'streamlabs_get_active_scene' by explicitly saying 'all scenes'.

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 context ('current scene collection') but does not explicitly state when to prefer this over alternatives or provide exclusions. An agent could infer it is for enumeration, but there is no direct guidance about when to use 'get_scene' vs 'list_scenes'.

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