Connect OPC UA industrial bus

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

Annotations already convey that the tool is not read-only and not destructive. The description adds some context by indicating it creates a scaffold (rather than a live connection) and includes 'read-only safety-policy notes,' but it does not disclose side effects such as whether it makes external network calls or requires an OPC UA server. This adds value but leaves gaps.

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, well-structured sentence that front-loads the primary action and resource, followed by a list of components. It is concise and free of redundant wording, though the dense jargon could be slightly clearer.

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?

Given the tool's complexity (12 parameters, no output schema, sparse annotations), the description is incomplete. It does not explain how the scaffold is structured, how parameters interact, or what the agent should expect after invocation. A more thorough description is necessary for safe and correct use.

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?

With only 17% schema description coverage, the description was expected to compensate for the 12 parameters, but it does not. It mentions high-level concepts like 'adapter ingest options' and 'node maps' without mapping them to specific parameters or explaining enum choices like adapter_mode or security_policy. The description adds minimal parameter-level meaning.

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 verb 'Create' and the resource 'OPC UA industrial telemetry scaffold', listing specific components (node maps, adapter ingest options, status tables, read-only safety-policy notes). This distinguishes it from sibling tools like connect_mqtt_iot_bus or connect_udp_telemetry_bridge, which target different protocols.

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 no explicit guidance on when to use this tool, prerequisites, or alternatives. While the name implies OPC UA connectivity, the description only states what it creates, leaving the agent to infer usage context without any 'use when' or 'instead of' cues.

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