OSC router matrix

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is not burdened with those. It adds valuable behavioral context: 'offline-safe' suggests that OSC isn't sent until activation, plus deterministic layout and a report of emitted addresses. It does not mention overwrite or collision behavior, but these are minor gaps given the annotation coverage.

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 compact and front-loaded: it starts with the action and then lists the key deliverables in a dense, structured sentence. The second sentence situates the tool in its intended ecosystem without wasting 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?

With no output schema, the description compensates by promising a 'structured report of every emitted OSC address' and by specifying the internal CHOP structure. The schema's min/max constraints and annotations cover edge cases and safety, making the description complete enough for an agent to understand the outputs and scope.

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%, so the baseline is 3. The description adds only high-level pointers like 'target-specific address prefixes' and 'structured report of every emitted OSC address,' but does not provide parameter-level details beyond what the schema already offers. It neither enriches nor contradicts 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?

The description uses the specific verb 'Create' and clearly enumerates the artifacts: one Constant CHOP plus OSC Out CHOP per target, deterministic left-to-right layout, target-specific address prefixes, and a structured report. It distinguishes itself from sibling connect_* integration tools and create_ndi_router_matrix by positioning this as a generic OSC-ready primitive for multiple show-control endpoints.

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?

It gives a concrete use case: 'Use it as the primitive for QLab, atemOSC/Companion, Resolume, VDMX, or any OSC-speaking show-control endpoint.' This implies when to choose this tool over more specific integrations, though it does not explicitly state exclusions or alternatives, leaving the agent to infer boundaries.

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