set_transport_context

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

Annotations state readOnlyHint=false and destructiveHint=false, so the tool is known to mutate state but not destructively. The description uses the word 'guarded' but does not explain the two-phase dry-run/apply pattern, the requirement for expectedStateVersion, planHash, or confirmationToken, or that applying requires a valid token. This is significant behavioral context missing from the description, beyond what annotations provide.

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, extremely concise and front-loaded with the action ('Plan or apply') and the resource ('metronome and count-in changes'). It has no fluff, but it is too sparse to cover essential information. The conciseness is good, but the lack of detail prevents a 5.

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 complex tool with 6 parameters and a guarded workflow (dry-run then apply). The description does not explain the required sequence (dry run first, then apply with token), the purpose of expectedStateVersion for concurrency control, or what happens on apply. Even with a rich schema, the description is too minimal for an agent to correctly use the tool without opening the schema, so it is not contextually complete.

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 100%, and each parameter already has a clear description (e.g., dryRun, planHash, confirmationToken, expectedStateVersion). The tool description adds no additional meaning about how these parameters relate or are used together. Per the rubric, with high schema coverage the baseline is 3, and the description does not go beyond that.

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 states a specific action (plan or apply) and a specific resource (metronome and count-in changes). It is clear what the tool does, though it does not explicitly differentiate from siblings like set_transport_recording_context or set_song_musical_context. The mention of 'guarded' adds a hint of the two-phase pattern, but the purpose is clear enough for a 4.

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. It does not mention other tools for different transport settings (e.g., set_tempo, transport_play) or explain that this is the only tool for metronome/count-in changes. The scope is implied by the name and description, but there is no explicit when-to-use or when-not-to-use guidance, so it earns a 2.

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