Tcp Connect

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

With no annotations, the description must carry the full behavioral burden. It only mentions that it connects and measures time; it does not disclose timeout behavior, error handling, whether the connection is actually opened and closed, or any side effects. This is a notable gap for a network probing 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 short sentence with no fluff and the key verb appears first. It is concise and readable, though its brevity crosses into under-specification for parameter details.

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?

For a network tool requiring a target host and port, the description and uninformative schema leave the invocation incomplete. The agent still lacks the parameter format and any behavioral details; an output schema exists but does not compensate for missing input semantics.

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 schema is a free-form object with 0% description coverage)Skip the entire reasoning section and produce only the final JSON.No annotations exist, and the schema provides no parameter details, so the description must explain how to specify host and port. It mentions 'host:port' conceptually but does not state the expected parameter structure or format, leaving an agent to guess.

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 action and resource: establish a TCP connection to a host:port and measure the time. This is enough to distinguish it from siblings like nginx_status or dns_resolve, though it does not explicitly differentiate from tcp_connect_as.

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?

Usage is implied by the purpose: use it to test TCP connectivity and measure connection time. However, it gives no explicit guidance on when to choose this over related tools such as tcp_connect_as, http_check, or tls_check, and no exclusion criteria.

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