ableton_analyze_and_apply_mastering

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

No annotations are present, so the description must fully convey behavioral traits. It mentions 'deterministic' adjustments and 'render', but does not disclose side effects (e.g., permanent project modification), authentication needs, or whether the analysis render is saved. The description is minimally informative beyond the verb sequence.

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 a single sentence, which is concise but lacks structure. It is front-loaded with the main action but omits important details. Acceptable for brevity, but could benefit from additional context.

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?

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is insufficient. It does not explain the return value, the effect of the analysis, or the relationship between parameters like `targetLufs` and `chain`. The description leaves many gaps for an agent to infer.

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 only 13% (only `outputPath` has a description). The description adds no additional meaning to any parameter, including the complex `chain` object with nested `device` and `settings`. The agent receives almost no guidance on parameter usage beyond the schema structure.

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's purpose: 'Render, analyze, and apply deterministic mastering adjustments to the master chain.' It uses specific verbs and identifies the target resource (master chain), distinguishing it from sibling tools like `ableton_apply_mastering_chain` (apply only) and `ableton_analyze_mix` (analyze only).

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?

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives such as `ableton_apply_mastering_chain` or `ableton_analyze_mix`, nor does it mention exclusions or prerequisites.

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