Set Fairlight EQ Band

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

Annotations already declare this is a non-destructive, idempotent, closed-world mutation. The description adds meaningful device-specific behavior: the 6-band layout, default filter types/frequencies, and which bands start disabled. It could go further by noting that changes affect live audio, but it substantially supplements the annotations.

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 front-loaded and the band layout is valuable, but the Args section largely repeats schema content that is already fully documented. It is appropriately sized overall but not maximally concise.

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?

With 8 parameters, no output schema, and annotations covering safety/idempotency, the description provides enough context to invoke the tool correctly. It omits explicit sibling routing and live-audio impact notes, but those are secondary gaps.

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 description coverage is already 100%, so the baseline is 3. The description adds useful meaning beyond the schema with the default band layout and per-band defaults, though many parameter descriptions (ranges, enum values, input mapping) duplicate what the schema already states.

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 states a specific verb and resource: setting an EQ band on a Fairlight audio input, with the band range (0-5). It implicitly distinguishes itself from master EQ and preset siblings via 'audio input' and 'band,' but it never names those alternatives explicitly.

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 tool name and the mention of 6 bands per channel, but there is no explicit guidance on when to use this versus atem_set_fairlight_eq_preset, atem_set_fairlight_master_eq, atem_get_fairlight_eq_state, or atem_reset_fairlight_eq.

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