apply_mastering_chain

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

With no annotations, the description carries the full burden. It discloses the chain components for each preset and implies a mutation of the master track, but it does not clarify whether existing master FX are preserved or replaced, nor does it mention reversibility 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?

The purpose is front-loaded, the preset list is compact, and the follow-up instructions are directly useful. Every sentence contributes without unnecessary repetition.

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 mutation tool with no annotations and no output schema, the definition covers presets and next steps but omits important side-effect details such as whether applying a chain overwrites existing master FX. It is adequate but has clear behavioral 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 0%, so the description must compensate. It does so by listing the preset values and explaining the FX chain for default, loud, and gentle, which adds substantial meaning beyond the bare string parameter.

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?

States a specific verb and resource: adding a standard mastering FX chain to the master track, with preset variants. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as add_master_fx or apply_limiter.

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?

Gives useful follow-up guidance: use set_master_fx_parameter after applying, and use list_master_fx/get_fx_parameters to discover indices. However, it does not state when to choose this tool over alternatives like add_master_fx or apply_limiter, nor does it provide exclusions.

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