streamlabs_set_source_muted

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

No annotations are provided, so the description must carry the full burden. It discloses the core behavior (mute/unmute) but does not mention side effects, reversibility, permissions, or error conditions. This is minimal but not misleading, so a 3 is appropriate.

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 two sentences, action-oriented, and free of unnecessary words. The first sentence states the purpose; the second provides a critical prerequisite. Perfectly concise and well-structured.

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 tool, the description covers the operation and how to obtain the required ID. It does not mention return values or error handling, but with no output schema and low complexity, it is reasonably complete. Minor missing context about source eligibility is not critical.

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 already fully documents both parameters with clear descriptions. The description adds extra value by telling the user where to get the sourceId, which is practical guidance beyond the schema. It doesn't add detail for 'muted', but the sourceId provenance is useful.

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 (mute/unmute) and the resource (audio source), and it distinguishes from related tools like set_source_volume. The reference to streamlabs_list_audio_sources further clarifies the intended source type, making it 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?

It provides explicit guidance on obtaining the sourceId from streamlabs_list_audio_sources, which is a clear 'when/how to use' instruction. However, it does not explicitly contrast with alternative tools like set_source_volume or explain when not to use it, so it falls short of a 5.

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