Create DMX fixture pipeline

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

Annotations state readOnlyHint=false, so the description's 'creates', 'inserts', 'merges', and 'drives' are consistent. The description goes far beyond annotations by disclosing the internal CHOP construction (Constant CHOPs with named channels, pad CHOPs for alignment), the output container and JSON report contents, and the fact that per-fixture sliders are not auto-exposed. This is substantial behavioral transparency.

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 paragraph that front-loads the core purpose, then details the construction steps, return value, and a critical caveat about slider exposure. Every sentence adds value—no filler. It is appropriately sized given the tool's complexity.

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 no output schema, the description fully covers the return value (container + JSON report with listed contents), the build process, naming conventions, and post-build binding instructions. The annotations and schema handle safety and parameter details, so the description covers all remaining context needed to invoke the tool correctly.

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?

The input schema already has 100% description coverage for all 7 parameters, each with a clear description. The tool description adds meaning by explaining how the 'fixtures' parameter maps to CHOP creation (using the fixture id as a channel prefix) and how 'startChannel' drives pad-CHOP alignment for DMX slots. It also links 'net', 'universe', 'host', and 'fps' to the dmxoutCHOP par names. This justifies a 4.

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 opens with a specific verb+resource: 'Build a DMX/Art-Net (or sACN) output chain from a fixture list.' It enumerates the supported fixture profiles and the exact CHOP structure built, plus the return value. This clearly distinguishes it from sibling tools such as create_fixture_control, which likely has a narrower scope.

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 clearly states what the tool does and what it returns, giving an agent clear context for when to use it. It also tells the agent that per-fixture sliders are NOT auto-exposed and directs to bind_to_channel/animate_parameter afterward, which provides follow-up guidance. However, it doesn't explicitly state when not to use it or compare it to alternative pipeline-creation tools, so it earns a 4 rather than a 5.

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