streamlabs_set_source_volume

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the meaning of the deflection parameter range (0 silent, 1 max/unity gain), which is helpful. However, it does not mention potential side effects, errors (e.g., invalid sourceId), or persistence of the setting.

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 sentence that is front-loaded and free of extraneous words. Every word contributes to the tool's purpose and parameter semantics.

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 setter with no output schema and no annotations, the description is largely sufficient. It covers the key behavior and parameter range. It could be more complete by mentioning error handling or prerequisites (e.g., source must be audio-capable), but these are not critical for basic use.

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 schema covers 50% of parameters (deflection has a description). The tool description adds context by clarifying that sourceId refers to an audio source and that deflection represents the fader position with a specific range. This adds meaning beyond the schema, though sourceId remains underdescribed.

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 verb (set), the resource (audio source's volume fader position), and the exact range (0 to 1). It distinguishes this tool from sibling tools like set_source_muted by focusing on fader deflection rather than muting.

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 for adjusting audio source volume but does not explicitly state when to use this tool versus alternatives like set_source_muted or other audio-related tools. No exclusions or alternative guidance are provided, but the purpose is self-evident.

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