Configure Art-Net / sACN output and universe grant requests

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

With no annotations, the description carries the full burden and does so well: it discloses that changes are validated before sending, that the console silently ignores or clamps invalid values yet every written property is read back, that there is no undo but previous holds prior values, and that network/exclusive confirmations are mandatory.

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?

Front-loaded with the core action and packed with useful detail; nearly every clause adds information. However, it is delivered as one long semicolon-chained sentence with nested parentheticals, which makes it dense rather than easily scannable.

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 complex, multi-parameter mutation with nested objects, no annotations, and no output schema, the description supplies prerequisites, universe ranges, clamp/verify behavior, and undo semantics. The remaining holes are the meaning of verify and any statement of what is returned, though 'every written property is read back' partially covers the latter.

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 only 25%, but the description compensates heavily: it explains entry add/remove/edit-by-number semantics, local_universe..+amount-1 mapping, Art-Net absolute universe ranges (0..32767) versus sACN (1..63999), mode, enabled, sACN priority 0..200, and grant_request's universes/value auto|on|off. The verify parameter is left unexplained in both schema and description, which is the main gap.

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?

States a specific verb and resource: changes the console's DMX output configuration, covering protocol output state, entry mappings, and grant requests. It is clearly distinguished from read-oriented siblings like gma3_dmx_output and gma3_dmx by framing everything around mutation of configuration entries.

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?

Gives concrete conditions for use: network:true is required when the change makes a protocol send DMX onto the network, exclusive:true is required, bridge 0.30.0 is needed, and preview:true shows the plan first. It doesn't explicitly name an alternative tool for simply reading the current config, so it stops short of full when-to-use/when-not guidance.

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