Get Fairlight EQ & Dynamics State

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine value beyond them by stating the return is human-readable in dB, Hz, and ms, which matters since there is no output schema. It does not mention connection prerequisites or error behavior.

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?

Two sentences plus a one-line arg note; the purpose and return format are front-loaded with no filler. The args block lightly restates the required param but earns its place through the camera-to-number mapping.

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?

A simple one-param read tool with no output schema; the description covers what is read, the units returned, and how to identify the input. Missing only the shape of the returned state (e.g., number of EQ bands) for full completeness.

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% with a single required integer, so the baseline is 3. The description exceeds that by decoding the parameter ('1=Camera 1, 2=Camera 2, etc.'), giving semantic meaning the bare schema text 'Audio input number' lacks.

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?

Specific verb+resource: 'Get the current EQ bands, compressor, limiter, and gate/expander settings' scoped to a Fairlight audio input. This clearly separates it from the set_* Fairlight siblings and from the broader atem_get_audio_state, so an agent can pick it without opening the schema.

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 read-only 'get current ...' framing (read before you set), but no explicit when-to-use or when-not guidance is given. It never names an alternative such as atem_get_audio_state for general mixer state, leaving routing to inference.

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