engine_fix_mix

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

No annotations provided, so description carries full burden. It fully discloses the corrective EQ per track (HP filter, narrow cuts, high-shelf air boost) and optional master chain (bus glue comp + brick-wall limiter). No hidden behaviors or contradictions.

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?

Well-structured with purpose first, then process, then usage. Every sentence adds value, but slightly verbose with detailed EQ list. Could be more concise without losing clarity.

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?

No output schema, but tool is a mutation that applies effects. Description covers what it does, when to use, parameters, and process. No missing critical information for an agent to invoke it correctly.

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 0%, but description explains both parameters: style (optional v2 catalog style for better classification) and include_master (apply emergency master chain, default True). Adds meaning beyond schema.

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 clearly states the tool rescues a muddy/harsh/unbalanced mix with specific corrective EQ processing per track. It distinguishes from sibling tool engine_mix by specifying this is for fixing a poorly mixed track, not replacing engine_mix.

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?

Explicit guidance: 'Call this when a mix sounds stuffy or harsh and you want a quick corrective pass before fine-tuning.' Also warns it doesn't replace engine_mix and should be used to fix something already mixed poorly by someone else.

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