Set Fairlight Gate / Expander

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

Annotations already cover the safety profile (idempotent, non-destructive, closed-world), so the description's job is to add domain behavior — which it does, explaining that sub-threshold audio is cut or reduced by range/ratio and that gateEnabled switches modes. It stops short of saying what happens on invalid mode/parameter combinations or whether changes take effect live.

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?

Front-loaded purpose sentence followed by an efficient per-argument list; every line earns its place. Minor redundancy with the schema on units and bounds keeps it from a 5.

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 9-parameter mutation tool with no output schema, the description covers the mode semantics and every parameter's meaning and units, which is enough to call it correctly. It lacks any note on side effects relative to other Fairlight dynamics settings or error conditions, a small remaining gap.

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%, so the baseline is 3; the description earns a bump by adding meaning the terse schema lacks — input numbering maps to camera numbers, threshold signposts 'audio below this is reduced', and range is framed as how much reduction occurs. It adds real semantic value beyond 'Threshold in dB' / 'Range in dB'.

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 noise gate or expander on a Fairlight audio input') and immediately defines what gates and expanders do. This distinguishes it cleanly from the sibling dynamics tools (atem_set_fairlight_compressor, atem_set_fairlight_limiter, atem_set_fairlight_eq) which act on different processors for the same input.

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?

Explains the gate-vs-expander semantics (

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