Connect REAPER transport

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

Annotations already indicate non-read-only, non-destructive, open-world behavior. The description adds the context that this creates a 'scaffold' rather than a live connection, which is useful, but it does not disclose side effects such as whether existing components are overwritten, whether REAPER must be running, or what 'operator-approved recording templates' actually entails.

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, front-loaded sentence with no filler or redundant phrasing. It is concise and to the point, though 'operator-approved' is unexplained jargon.

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 10-parameter tool with no output schema and sparse annotations, a one-sentence description is insufficient. It leaves out key behavior such as return values, error conditions, port/host semantics, how recording templates are selected, and whether this tool actually connects to REAPER or only creates a scaffold.

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?

Only 20% of the 10 parameters have schema descriptions, and the tool description adds almost no parameter-specific meaning. It loosely aligns with track/marker counts but does not explain send_port, receive_port, reaper_host, include_record, project_name, or active.

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 'Create' and identifies a clear resource: a 'REAPER OSC transport, track, and marker bridge scaffold.' It clearly distinguishes this tool from the dozens of sibling connection tools by naming the exact target system and the scaffold components.

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 the many sibling connect_* tools, such as connect_ableton_link_session or connect_qlab_cue_stack. It does not mention prerequisites, exclusions, or when an alternative should be preferred.

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