live_bounce

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

No annotations are supplied, so the description carries the full burden, and it does: it discloses that no dialogs appear, that the operation is undone by a single live_undo, that the rendered .wav survives undo in the Bounces folder, and that toNewTrack mutes the originals. Those are exactly the side effects an agent needs before mutating a session.

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?

Three dense sentences, front-loaded with the verb and resource before the mode breakdown and the caveats. Every clause carries non-obvious information (muted originals, surviving .wav, undo count, dialog exclusion); nothing is filler.

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 two-parameter mutation with no annotations and no output schema, the description covers modes, reversibility, and residual artifacts thoroughly. The only real gap is how to identify the target track, and secondarily whether anything is returned; both are minor against the otherwise strong behavioral coverage.

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 well for the enum parameter, spelling out what inPlace and toNewTrack each produce, but leaves the required 'track' parameter undefined — no indication whether it takes a track name, index, or ID, despite many sibling tools that could identify a track.

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 (bounce/render) applied to a specific resource (all events on one track in the running Studio One), and disambiguates the two modes in one clause each. It also explicitly excludes what it is not (mixdown/stem export), so an agent can separate it from adjacent rendering operations without opening the schema.

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 explicit when-to-use (per-track bounce, with the two mode variants), an explicit when-not (mixdown and stems are not offered because they open dialogs), and names the sibling that reverses it (one live_undo). Routing information is complete rather than implied.

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