Connect UDP telemetry bridge

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, which the description does not contradict. The description adds minimal context beyond the annotations, noting it creates a 'scaffold' and listing the intended data categories (packets, replies, status maps, diagnostics), but does not detail side effects, permissions, or lifecycle behavior.

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, focused sentence that starts with the action verb 'Create' and directly states the object and scope. It contains no filler or redundant information, earning full marks for conciseness.

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, low schema coverage, and no output schema, the description is too thin to fully equip an agent. It does not explain what the resulting scaffold looks like, how parameters affect the outcome, what success/failure returns, or any prerequisites. The description is adequate for a high-level overview but insufficient for safe and 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 description coverage is only 29% (only 'name' and 'parent_path' have descriptions). The tool description does not explain any of the seven parameters, such as listen_port, remote_port, packet_count, or active, nor how they relate to the UDP scaffold. This is a significant gap for a 7-parameter tool.

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's action: 'Create a UDP In/Out DAT scaffold' for telemetry-related data. It distinguishes itself from sibling bridge tools by specifying the UDP protocol and telemetry purpose, making it unmistakable among many connect_* alternatives.

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 implies use for setting up a UDP telemetry bridge scaffold, but provides no explicit guidance on when to prefer this tool over other bridge/connect tools (e.g., connect_oscquery_namespace or connect_websocket_control_bus). No exclusions or alternative recommendations are mentioned.

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