mcp_opendaw_freeze_audiounit

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 offline rendering mechanism, the caching behavior, and the fact that frozen AUs play from cache instead of real-time processing. It also mentions potential errors (sidechain dependents block freeze). This goes beyond a generic 'freeze' and explains real-world effects.

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 organized into a summary, implementation details, a constraint, a parameter note, and a return note. It is about 80 words and contains no filler. The internal API reference (audioUnitFreeze.freeze()) is slightly extra but adds credibility without bloating the text.

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 single-parameter tool with an output schema, the description covers purpose, mechanism, constraints, parameter meaning, and possible return. It does not mention related operations (unfreeze, freeze status) or performance implications (long render time), but these are available as sibling tools. Overall, it is nearly complete for a focused freeze operation.

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?

The only parameter is unit_index, and the schema description coverage is 0%. The description adds 'AU index to freeze,' which clarifies what the index refers to, but does not explain how to discover the AU index (e.g., via list_effects or get_effect_chain) or whether it is zero-based. This is minimal compensation for the schema gap.

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 opens with a specific verb+resource: 'Freeze an audio unit — pre-render its output offline to save CPU.' This clearly distinguishes it from siblings like unfreeze_audiounit and get_unit_freeze_status, and explains the primary benefit.

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?

It states a clear use case (save CPU by pre-rendering) and gives an explicit exclusion: 'Cannot freeze AUs with sidechain dependents or the Output unit.' It doesn't explicitly point to alternative tools for unfreezing or status checks, but the context is sufficient for an agent to decide when to invoke it.

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