streamlabs_list_audio_sources_for_scene

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

No annotations exist, so the description carries the full burden. 'List' implies a read operation, but the description does not disclose what is returned (e.g., source names, IDs, mute/volume states) or whether it returns scene items. This is minimal behavioral detail for an unannotated tool.

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 filler. Every word contributes to the core meaning, making it easy to parse quickly.

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 single-parameter list tool, the description is adequate but not complete. It does not describe the return format (no output schema exists), and the ambiguous sibling names (list_audio_sources, list_all_audio_sources) suggest that some additional context about scene-scoping would improve completeness. Overall it is minimally viable.

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 coverage is 0%, so the description must explain the parameter. It does so minimally by saying 'by id', which maps sceneId to the scene's identifier, but it lacks guidance on where to obtain the id or any format constraints. This is just enough to disambiguate the parameter.

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') with a clear resource ('audio sources') and scope ('for a specific scene by id'). It distinguishes from siblings like streamlabs_list_audio_sources by making clear this is scene-scoped, and the parameter name sceneId reinforces that.

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?

Usage context is implied: use this when you need audio sources for a specific scene and have the scene id. However, there is no explicit guidance on when to prefer this over streamlabs_list_audio_sources or streamlabs_list_all_audio_sources, nor any exclusions.

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