Initiate recording on a specified track in REAPER DAW by arming it and starting transport. Provide the track index to begin capturing audio; call stop_transport when done.
Arm a track and start recording. Call stop_transport when done.
| Name | Required | Description | Default |
|---|---|---|---|
| track_index | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states 'arm and start recording' without disclosing side effects, prerequisites, or whether it is destructive. Minimal behavioral context.
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 totaling 11 words, no redundancy. Front-loaded the main action and followed with a necessary instruction. Efficient and structured.
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?
Despite low complexity (single parameter, no output schema), the description omits key details: expected track state, error conditions, and what happens post-recording. Insufficient for an agent to use confidently.
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%, and the description does not mention the 'track_index' parameter at all. No explanation of indexing or allowed values, leaving the agent uninformed.
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 clearly states 'Arm a track and start recording,' which is a specific verb+resource action. It distinguishes from siblings like play_project or stop_transport.
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 a clear usage hint: 'Call stop_transport when done,' indicating a sequential action. It implies using this tool to record on a track, but lacks explicit exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.