Set Audio Master Output

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

Annotations already declare idempotent=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely useful context that the tool works across both Fairlight and classic mixer modes. It does not say what happens when both optional args are omitted (no-op vs. query) or whether the change takes effect immediately.

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?

One-sentence purpose with the key compatibility detail up front, followed by a compact Args list. The Args section duplicates the schema descriptions, which is mild waste but keeps the definition readable.

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 two-optional-parameter setter with full annotations and full schema coverage, little is required, and no output schema means return values need no explanation. However, the all-optional nature of the call leaves the no-argument behavior undefined, which is the one gap an agent would actually hit.

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?

Schema coverage is 100% and both parameters are already documented with units and ranges, so the description's Args block mostly restates structured data. It adds the explicit -100 to +10 range and 'fader' terminology, but no guidance on partial updates or interaction between gain and followFadeToBlack.

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?

States a specific verb and resource ('Configure the master audio output level'), which distinguishes it from the sibling atem_set_audio_mixer_input and the Fairlight master EQ/dynamics tools. The added note about Fairlight and classic mixers reinforces scope but the description never explicitly contrasts the input-level sibling.

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?

Usage is implied by the name and the 'works with both' compat note, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative for per-input level changes (atem_set_audio_mixer_input). An agent must infer the boundary itself.

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