set_arrangement_record

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

No annotations are provided, so the description carries the burden. It accurately describes the ON behavior ('With it ON, launching Session clips/scenes records them into the Arrangement timeline') and provides context about why this is needed (export capability). It does not mention overwriting or reversal, but for a simple boolean arm/disarm, the behavior is adequately disclosed.

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 sentences, each earning its place: core function, behavioral effect, and context/alternative. No redundant wording, and the key action is front-loaded.

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 simple one-parameter tool, the description explains purpose, behavior, and when to use an alternative. An output schema exists, so return values need not be described. It is complete enough for confident invocation, though it could mention the 'global' scope more explicitly.

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 0%, so the description must compensate. It does so by mapping the 'on' parameter through phrases like 'Arm/disarm' and 'With it ON', effectively conveying that true arms and false disarms. This adds meaning beyond the bare parameter name.

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 starts with a specific verb and resource: 'Arm/disarm Arrangement (global) Record'. It then explains the effect (launching Session clips/scenes records them into the Arrangement timeline) and differentiates from capture_session_to_arrangement by name.

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?

Clearly states when to use: to capture a Session-view loop for export because 'Live's exporter only renders the Arrangement'. Also explicitly recommends capture_session_to_arrangement as the alternative for full automated capture.

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