streamlabs_list_all_audio_sources

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the cross-scene scope and that it lists audio sources, which implies a read-only operation. However, it does not specify whether it includes sources not assigned to any scene or the exact return structure, leaving minor gaps.

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, well-structured sentence that front-loads the action ('List every audio source') and efficiently conveys the scope with a parenthetical clarification. There is zero wasted wording.

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 the simplicity of the tool (no parameters, no annotations, no output schema), the description is largely complete. It identifies what is being listed and the cross-scene scope, but could mention the return format (e.g., array of audio sources) to be fully self-contained.

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, so the description is the only source of parameter-level meaning. It adds useful context by clarifying the scope ('across all scenes'), which is effectively the main behavioral parameter. A baseline of 4 is appropriate for zero-parameter tools with contextual description.

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 action ('List every audio source') and the specific scope ('across all scenes'), which differentiates it from sibling tools like streamlabs_list_audio_sources and streamlabs_list_audio_sources_for_scene. The verb and resource are specific and unambiguous.

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 gives clear context for when to use this tool by pointing out it covers all scenes 'not just the currently active one'. While it does not explicitly name alternative tools, the inference is straightforward given sibling names, so it provides clear context without an explicit when-not statement.

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