Reset Fairlight EQ

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

The annotations already declare that this is a non-read-only, idempotent, non-destructive operation. The description adds useful behavioral detail by specifying that it resets to factory defaults and that omitting band resets all bands.

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 short, front-loaded with the action and target, and uses an Args list only for the details an agent needs. Every sentence and parameter note is directly relevant.

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-parameter mutation tool with full schema coverage and annotations, the description is mostly complete. The remaining gap is that it does not explain when to choose this reset over the related set/preset EQ tools or note connection prerequisites.

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, but the description adds meaning beyond the schema by mapping input numbers to cameras (1=Camera 1, etc.). It also reinforces the band range and the omit-for-all behavior.

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: reset the EQ to factory defaults on a Fairlight audio input. This clearly distinguishes it from sibling tools such as atem_set_fairlight_eq and atem_set_fairlight_eq_preset.

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 first sentence implies the tool is for resetting EQ rather than setting EQ values, but it does not explicitly compare it with alternatives like atem_set_fairlight_eq or atem_set_fairlight_eq_preset. It also does not mention prerequisites such as needing an active connection.

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