Resolume / VDMX output-control chain

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

Annotations already declare readOnly=false and destructive=false, so the mutation profile is known. The description adds that it builds target-specific OSC Out lanes with layer opacity, crossfader, speed, clip trigger, and blackout channels, but does not disclose prerequisites, side effects, or whether existing structures are modified.

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 two sentences, front-loaded with the primary purpose and followed by a relevant usage qualifier. It is dense but every clause contributes meaningful information, with 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 builder tool with 7 well-documented parameters and no output schema, the description covers purpose, target applications, channel types, and usage context. It does not detail the resulting network structure or edge cases, but it is sufficient for an agent to understand the tool's role and main function.

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 coverage is 100% with descriptions for all 7 parameters, so the baseline is 3. The description adds context about channel types but does not map them to specific parameters or provide additional syntax/format details 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?

The description clearly states the tool creates an OSC control chain for driving Resolume, VDMX, or both, with specific channels listed. It partially differentiates from output tools by mentioning use beside video/NDI/Syphon tools, but it does not explicitly distinguish from closely related sibling tools like connect_resolume_arena or connect_vdmx_workspace.

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 context: use it beside video/NDI/Syphon output tools when an external VJ app handles playback or final compositing. It implies when not to use (when no external VJ app), but it does not explicitly name alternative tools or exclusion criteria.

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