QLab OSC bridge

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

Annotations indicate readOnly=false and destructive=false, which align with 'create'. Description adds useful context about not needing QLab during build and exposing routes to a configurable port, but doesn't disclose runtime behavior or potential side effects beyond that.

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 concise sentences, front-loaded with the core action and resource. Every phrase adds value; no wasted words.

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 build tool with all parameters documented, description covers the main purpose, exposed routes, and a key build-time condition. No output schema or return value explanation necessary. Could mention dependencies on other primitives, but the primitive is named.

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?

Input schema defines all 6 parameters with descriptions (100% coverage). Description adds slight context by referencing optional cue routes that map to cue_numbers, but doesn't add significant meaning beyond the 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?

Description identifies a specific action (create a QLab OSC control bridge), names the primitive used (OSC router matrix primitive), and lists the exact routes exposed. This distinguishes it from sibling tools like connect_qlab_cue_stack or osc_router_matrix.

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?

Provides clear context on what the tool does (builds a bridge with specific OSC routes) and a key non-requirement (QLab doesn't need to run during build). No explicit alternatives are named, but the use case is unambiguous.

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