connect_tcp

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

With no annotations, the description carries the full burden for behavioral disclosure, but only states the action of connecting. It does not mention whether the connection is persistent, if repeated calls are safe, or what happens on failure. The phrase 'raw TCP SCPI socket' adds some protocol context but no side-effect details.

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 with no wasted words. It is front-loaded with the verb and resource. However, it is so terse that it under-serves the tool's complexity.

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 existence of four parameters, no annotations, and an output schema that is not described, this one-sentence description is grossly insufficient. It omits connection lifecycle details, parameter meanings, and how it fits into the workflow with sibling tools.

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?

The input schema has 0% description coverage, so the description must compensate. It does not explain host, port, timeout_s, or header_off beyond the schema defaults. The phrase 'raw TCP SCPI socket' hints at host/port but leaves timeout and header_off unaddressed.

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 and resource: 'Connect to the oscilloscope through raw TCP SCPI socket.' This distinguishes it from sibling tools like identify_tcp and disconnect_tcp, which serve different purposes.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., network reachability), nor does it point to disconnect_tcp for closing the connection. Usage context is only implied by the tool name.

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