network/ping

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

With no annotations, the description carries the full behavioral burden, but it only states the metric being measured and the protocol. It does not disclose whether the tool performs a TCP handshake, what output or exit status it returns, whether elevated privileges are needed, or how timeouts and errors are handled.

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?

A single, front-loaded sentence with no filler or repetition. It communicates the core operation immediately and earns its place.

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 tool with three parameters, no annotations, and no output schema, a one-line purpose statement is not enough. Missing context includes expected output, port/timeout behavior, error cases, and permission requirements, so an agent would have to inspect the schema or guess to invoke this 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 coverage is only 33%, so the description needed to compensate for port and timeout semantics, but it does not. It names the host as the target, yet says nothing about the port defaulting to 80, the meaning of timeout, or how these parameters affect the measurement.

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 uses a specific verb ('Measure') and a precise resource ('TCP reachability and latency to a host'), which clearly distinguishes this from sibling network tools like network/curl (data transfer), network/nslookup (DNS resolution), and network/trace-path (route tracing). It also clarifies that this is a TCP-level probe, not a generic ICMP ping.

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 wording implies the tool is for reachability/latency diagnostics, so an agent could infer when to use it. However, it gives no explicit when-to-use or when-not-to-use guidance, and it does not name alternatives such as curl or trace-path for cases where transferring data or tracing routes is needed.

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