ableton_flatten_track

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

No annotations are provided, so the description should disclose behavioral traits. It only says 'flatten to audio' with no details on side effects (e.g., whether the frozen track is replaced, whether undo is possible, or any destructive actions). The conditional bridge behavior is mentioned but not explained.

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. However, the phrase 'when the bridge exposes a real flatten operation' is unnecessary and may confuse the agent. It could be simplified to just 'Flatten a frozen Ableton Live track to audio.'

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 that the tool has one parameter and no output schema, the description should explain what flatten means (e.g., converting frozen track to audio, including any limitations). It does not mention prerequisites like the track being frozen, nor what happens to the original track. The conditional bridge remark adds complexity without clarity.

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%, yet the description does not mention the single parameter 'trackIndex' at all. The agent must infer its meaning from the tool name, and the schema's 'minimum: 0' suggests zero-based indexing, but this is not clarified. The description adds no value beyond the schema.

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 flattens a frozen Ableton Live track to audio, which is a specific action. The phrase 'when the bridge exposes a real flatten operation' adds some ambiguity but still conveys the main purpose. It distinguishes from the sibling tool 'ableton_freeze_track' which freezes rather than flattens.

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 description provides no guidance on when to use this tool versus alternatives like 'ableton_freeze_track' or 'ableton_consolidate_clip'. It does not mention prerequisites (track must be frozen) or when not to use it. The conditional phrase about the bridge is unclear and does not help the agent decide.

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