Connect UDP telemetry bridge

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

Annotations already convey readOnlyHint=false and destructiveHint=false, and the description aligns with 'Create'. It adds a little context about the scaffold's contents (telemetry packets, replies, status maps, diagnostics) but doesn't disclose side effects like port binding, existing-node modifications, or whether it overwrites anything. No contradiction.

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 with no fluff. It quickly states the action and object. It could be slightly more structured (e.g., including a result or prerequisite clause), but it is appropriately concise.

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 7 parameters, no output schema, and a large ecosystem of sibling tools, this one-sentence description is insufficient. It doesn't explain what 'scaffold' entails, whether the tool returns the created node, or what prerequisites exist (e.g., active state, port availability). The agent may not know how to configure the parameters effectively.

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?

Only 2 of 7 parameters have schema descriptions (29% coverage), and the description doesn't compensate. Parameters like listen_port, remote_port, remote_address, packet_count, and active are unexplained in the description. An agent gets little help understanding what these parameters mean or how they relate to the scaffold.

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 ('UDP In/Out DAT scaffold') and adds the scope of the scaffold ('telemetry packets, replies, status maps, and diagnostics'). This distinguishes it from other bridge/connection tools by its UDP telemetry focus.

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?

No usage context is provided. The description doesn't say when to use this tool over siblings like connect_websocket_control_bus or connect_serial_device_bus, nor does it give any exclusions or alternatives. The only hint is the tool name itself, which isn't explicit guidance.

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