ableton_bounce_tracks

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It fails to explain side effects (e.g., whether original tracks are modified, new tracks created, or files overwritten). Essential behavioral traits like prerequisites (e.g., transport state) are omitted.

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 concise sentence with no redundancy. It is front-loaded and efficient, though it could include a brief behavioral note without becoming verbose.

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 9 parameters, no output schema, and no annotations, the description is far from complete. It does not explain return values, side effects, or required project state, leaving critical gaps for an agent to correctly invoke the tool.

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?

With only 11% schema coverage, the description should compensate but does not. It adds no explanation for any of the 9 parameters, leaving the agent to rely solely on the schema, which lacks descriptions except for outputPath.

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 action ('bounce') and resource ('selected tracks or stems') and the output ('audio artifacts for production review'). It is specific and distinguishes from siblings like 'export_render' which likely handles final export. However, it could be more explicit about the distinction.

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?

The phrase 'for production review' implies usage context but no explicit when-to-use or when-not-to-use guidance is provided. The sibling 'export_render' suggests this is for temporary reference, but the description does not directly recommend when to choose this over alternatives.

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