live12_transport_record

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

No annotations, so the description carries the full burden. It usefully discloses the underlying LOM semantics (Song.record_mode / Song.session_record), hinting that this sets a record-enable flag rather than a full transport action. It omits whether recording actually begins immediately, whether armed tracks are required, and how to disengage.

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?

Two short sentences, front-loaded with the action, and the mode split is stated in the same breath. Nothing is wasted or buried.

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, no-output-schema mutation tool with no annotations, the definition covers the target modes but leaves out required context: track arming, whether transport must be running, and how to stop recording. Adequate but with clear operational gaps.

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 100% and the enum description already spells out 'arrangement' vs 'session'. The description adds the corresponding LOM properties, which is a modest value-add, but no default behavior or consequences of each mode are 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 and resource ('Enables recording in Ableton Live 12') with two named modes, so the agent knows exactly what the tool toggles. It does not differentiate itself from the closely related sibling live12_transport_set_overdub, which overlaps with the session-record path.

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 says recording can target arrangement or session, but never says when to choose one over the other, nor when to prefer live12_transport_set_overdub or follow with live12_transport_stop. Usage is implied by the mode names rather than stated.

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