Apply a Mix Doctor fix (gated)

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

Annotations provide readOnlyHint=false, destructiveHint=false. Description adds valuable behavioral context: the safety layer (snapshot, write, readback), rollback capability via fl_rollback_last_change, and that Mix Doctor never auto-applies. These details go beyond annotations and are crucial for safe invocation.

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 two well-structured sentences with no wasted words. The most critical information (applying a fix, safety layer, rollback) is front-loaded, and additional details follow logically.

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?

The description covers purpose, usage constraints, behavioral safety, parameter roles, and sibling differentiation. With an output schema present (not shown but indicated), the description effectively covers all necessary context for correct invocation.

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 100%, so baseline 3. The description adds meaning by explaining that 'trim_volume' sets a mixer track's fader to target_db, and provides context for the kind parameter. This enhances understanding beyond what the schema lists.

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 it applies 'ONE Mix Doctor fix' with a specific safety process (snapshot, write, readback, rollback). It distinguishes from sibling tools like fl_group_tracks and fl_apply_eq_intent by naming them 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?

Explicitly states 'Call this ONLY after the user approves the exact change in conversation', providing clear when-to-use guidance. Also mentions alternatives for grouping and EQ, helping the agent choose correctly.

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