transport

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

With no annotations, the description carries the full burden and it does deliver real behavioral context for two of seven actions: undo/redo operate on Live's own global history (not a per-tool stack) and back_to_arranger re-arms Arrangement follow after Session clips were launched. However, play/stop/continue/stop_all_clips behavior, failure modes, and whether transport state is global or per-track are unstated.

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 sentences, front-loaded with the tool's identity and then the non-obvious action semantics. No filler, though the quoted action names could be structured more scannably.

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?

No output schema and no annotations, so the description is the only behavioral source. It covers the two hardest-to-guess actions adequately but leaves four of seven enum values and the overall tool semantics (global vs per-track transport) unexplained, which is thin for a seven-action control surface.

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?

A single enum parameter with 0% schema description coverage, so the description must compensate. It adds meaning for 'undo', 'redo', and 'back_to_arranger', which is genuine value, but the other four enum values are left with no semantics beyond their literal names.

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?

"Transport control" names the resource and the enum enumerates the concrete actions, so the domain is clear. But the description never enumerates or characterizes the core actions (play/stop/continue/stop_all_clips) and gives no differentiation from siblings like stop_all_clips or fire_clip, so an agent must open the schema to know what this tool actually does.

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?

There is no guidance on when to choose this tool over alternatives such as stop_all_clips, fire_clip, or stop_track_clips, and no prerequisites or sequencing hints. The explanatory clauses about undo/redo and back_to_arranger describe behavior, not when to use them.

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