obs_audio_control

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

No annotations are provided, so the description carries the transparency burden. It discloses the get/set nature and volume unit semantics (0 dB unity, -100 silence), but does not describe return values, side effects, or behavior when both optional parameters are omitted. This is adequate but not rich.

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?

Two short sentences, front-loaded with the core action and followed by a necessary unit clarification. No filler or redundancy.

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 3-parameter tool with no output schema, the description covers the core behavior and parameter semantics sufficiently for an agent to select and invoke it. It lacks explicit return-value documentation, but the 'get' half of the description and the schema's 'omit to leave unchanged' hints make the query behavior inferable.

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 description adds meaning beyond the schema by explaining that volumeDb is in dB with 0 as unity and -100 as silence; the schema only provides the numeric range. It also maps 'mute state' and 'volume' to the muted and volumeDb properties, though inputName is left implicit as the audio input identifier.

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 'Get or set' with a clear resource ('audio input') and attributes ('mute state and volume'), making the tool's function immediately identifiable. It also distinguishes from siblings like obs_audio_routing and obs_set_input_settings by focusing specifically on mute/volume control.

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 controlling an audio input's mute and volume but provides no explicit guidance on when to prefer this over siblings such as obs_get_input_settings or obs_set_input_settings, nor any exclusions. The context is inferable from the purpose, so it meets the 'implied usage' level but not higher.

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