set_transport

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

Annotations already indicate this is a non-read-only, non-destructive, closed-world operation. The description adds a meaningful recording prerequisite about arming tracks, but it does not explain what happens when record/session_record are enabled, what null/default values mean, or how loop and time-signature changes interact.

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 very short and contains no filler, but it is written as two fragments rather than a front-loaded explanatory sentence. The brevity helps scanability while making the tool's behavior feel under-specified.

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?

This is a nine-parameter mutation tool with no parameter descriptions, and the description is too terse to fully support correct invocation. An output schema exists, so return values need not be explained, but the missing null/default semantics and recording side effects leave important 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 description coverage is 0%, so the description must carry parameter meaning. It groups the nine parameters into recognizable concepts and indicates that loop-region values are in beats, but it does not explain which parameters are optional, what null means, or precisely map loop_start/loop_length versus loop and numerator/denominator.

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 lists transport-related settings (arrangement record, session record, overdub, metronome, loop region, time signature), so the resource is inferable. However, it never states a clear verb such as 'sets transport options' and does not distinguish this tool from siblings like start_playback, stop_playback, set_tempo, or set_arrangement_time.

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 only guidance is the prerequisite 'Arm the tracks first with set_mixer(arm=True),' which is useful for recording but does not explain when to use set_transport versus playback or arrangement-timing siblings. There are no explicit when-to-use or when-not-to-use criteria.

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