Connect REAPER transport

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

Annotations already mark this as non-read-only and non-destructive, and the description aligns with 'create' as an additive operation. It adds context about OSC transport, tracks, and markers, but doesn't disclose side effects like whether existing scaffolds are modified or whether network connectivity is required. Since annotations cover the safety profile, the minimal additional disclosure is acceptable but not rich.

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, reasonably concise sentence with no filler. It front-loads the key action and resource. The vague 'operator-approved recording templates' could be clarified but overall it's efficient.

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 tool with 10 parameters, no output schema, and low schema coverage, the description is too thin. It doesn't explain what the scaffold returns, what 'operator-approved' means, or what parameters are essential. An agent would need to inspect the schema for defaults and still lack behavioral context (e.g., does it overwrite, does it need REAPER listening).

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 only 20%, so the description carries more burden but barely addresses individual parameters. It mentions 'track' and 'marker' which map to track_count and marker_count, but provides no guidance on send_port, receive_port, reaper_host, or include_record. This leaves most parameters underdocumented for a low-coverage schema.

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 identifies the tool's function with a specific verb ('Create') and a specific resource ('REAPER OSC transport, track, and marker bridge scaffold'). It distinguishes from sibling connect_* tools by explicitly naming REAPER and its components. However, the phrase 'operator-approved recording templates' is ambiguous and could be more precise.

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 implies usage for creating a REAPER OSC bridge but provides no explicit when-to-use guidance or alternatives. It doesn't mention prerequisites (e.g., REAPER running with OSC enabled) or contrast with other connect_* tools. This leaves the agent to infer appropriateness from the tool name and context.

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