Set Main Stereo Output Volume

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

Annotations already indicate a non-read-only, idempotent, non-destructive write operation. The description adds useful behavioral context by documenting support for both linear and decibel units, and specifying unity gain as 0 dB or 0.75 linear. It does not contradict annotations and goes beyond them with unit conversion details.

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 long, front-loaded with the primary action, and every clause adds value. It efficiently covers the tool's purpose, supported unit types, and unity gain reference without unnecessary elaboration.

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 with no output schema, this description is complete. It covers the target resource, the available value formats, and the unity gain calibration, which is sufficient for an agent to invoke the tool correctly. No critical missing information is apparent.

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?

Though the schema already describes both 'unit' and 'value' with 100% coverage, the description enriches the semantics by stating the exact valid ranges (0.0-1.0 and -90 to +10 dB) and defining unity gain. This provides context beyond the schema's field descriptions, helping agents understand how to construct correct values.

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: 'Set the main stereo output fader level on the X32/M32 mixer.' This is a specific verb+resource+scope that distinguishes it from sibling tools like channel_set_volume and bus_set_volume, which target different faders. The addition of unit ranges further clarifies what the tool does.

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 names the exact resource (main stereo output fader) and provides context about the mixer model, which implies when to use it over sibling volume tools. However, it does not explicitly state alternatives or exclusions (e.g., 'use channel_set_volume for channel faders'), leaving some room for interpretation. Still, the resource specificity gives clear context.

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