Connect lighting console OSC

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

The description discloses that the tool creates a scaffold and does not send direct DMX, complementing the annotations (readOnlyHint=false, destructiveHint=false). It mentions 'safety-gated' but does not elaborate on side effects like network connections or port binding—important given openWorldHint=true. No contradiction with annotations exists.

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, front-loaded sentence that packs essential information (verb, resource, console types, safety gating, no direct DMX) without wasting words. It is concise yet informative, making it easy to parse quickly.

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 tool with 10 parameters, no output schema, and minimal annotation context, the description is too high-level. It does not describe what the scaffold contains, how it should be configured, or what the agent can expect as a result, leaving significant gaps for correct invocation.

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 20% (2 of 10 parameters have descriptions), and the tool description does little to compensate. It only gives domain context (lighting consoles, safety-gating), which helps infer console_family and safety_mode, but it leaves parameters like cue_count, executor_count, send_port, receive_port, and console_host unexplained.

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 a specific verb ('Create') and resource ('OSC command scaffold for lighting consoles'), and adds exclusions ('without sending direct DMX') and safety qualifiers ('safety-gated'). It distinguishes itself from sibling tools by naming the specific console families it supports, making its purpose unmistakable.

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 explicit context for when to use the tool (for grandMA3, ETC Eos, ChamSys, Avolites, or generic lighting consoles) and implies a limitation (does not send direct DMX), which helps rule out scenarios where direct DMX is needed. However, it does not explicitly name alternatives or state when-not-to-use relative to sibling tools.

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