Connect OPC UA industrial bus

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description adds context about scaffold contents including safety-policy notes. However, it doesn't disclose what exactly gets created or modified (e.g., COMPs, node network) or any side effects beyond 'create', which is still vague for a mutation tool.

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 redundant words. It efficiently communicates the tool's purpose and primary inclusions, making it easy to scan.

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 12 parameters, no output schema, and minimal schema descriptions, one sentence is insufficient. The description doesn't explain return values, expected behavior, or the relationship between parameters and the scaffold's functional parts, leaving an agent under-equipped 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?

Schema description coverage is only 17% (2 of 12 parameters have descriptions), and the description does not compensate by explaining key parameters like poll_ms, namespace_index, security_policy, or adapter_mode. It mentions high-level features like 'adapter ingest options' but provides no mapping to actual parameters or guidance on how to set them correctly.

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 creates an OPC UA industrial telemetry scaffold and lists its contents (node maps, adapter ingest options, status tables, read-only safety-policy notes). This is a specific verb+resource combination that is easy to understand, though it doesn't explicitly distinguish itself from sibling connect_* tools in the same domain.

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 only implies usage (when you need an OPC UA scaffold) but provides no explicit guidance on when to choose this tool over alternatives like connect_mqtt_iot_bus or connect_udp_telemetry_bridge. There are no exclusions, prerequisites, or alternative references.

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