freeze_tracks

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

With no annotations the description carries the full burden. It usefully discloses the core mechanism (render to audio, offlining plugins) and the reversibility ('unfreezes them to edit again', implying frozen tracks are not editable), but says nothing about prerequisites, whether automation/routing changes, the time/disk cost of rendering, or the state of frozen tracks if the source is later edited.

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?

A single sentence, front-loaded with the operation and followed by the mechanism, the parenthetical rationale, and the reverse operation. Tight and readable; only 'to edit again' is mildly redundant with the preceding clause.

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?

There are no annotations and no output schema, so the description must stand alone; it covers the what and why but leaves 'mono' unexplained, gives no indication of success/return behavior, and omits constraints such as whether frozen tracks can still be edited or unfrozen repeatedly.

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 only 33% (just the 'unfreeze' param is documented), so the description should compensate. It clarifies freeze vs unfreeze semantics, but the 'mono' flag is undocumented in both description and schema, and the 'tracks' identifier format (name string vs integer index) is never explained.

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?

Specific verb+resource (freeze/unfreeze tracks) with the mechanism spelled out: renders to audio and takes plugins offline. No sibling tool does freezing/unfreezing, so the agent can distinguish it immediately from create_track, set_track_properties, or export_stems.

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 clear usage context: freeze when CPU is strained by heavy synths or long effect chains, unfreeze when you need to edit again. It states when each direction applies but names no alternative tool (e.g., bouncing or exporting stems) for the same goal.

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