net.ping

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

With no annotations, the description carries the behavioral burden. It usefully discloses the TCP-connect fallback and that the fallback is reported honestly, but it does not mention permission requirements for raw ICMP, rate limits, timeout behavior, or what the response fields contain beyond the listed stats.

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?

It is a single front-loaded sentence with no filler, but the extreme terseness leaves terms like 'mdev' and the fallback mechanism unexplained. It is concise, though perhaps too compressed for a three-parameter tool.

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 probe with no annotations, no output schema, and zero parameter descriptions, the definition is too thin. It should at least clarify the host/count/timeout behavior and what the honest fallback reporting looks like.

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 0% for three parameters, and the description says nothing about host, count, or timeoutMs. An agent must infer all parameter meaning from names and schema constraints alone, which the description does not supplement.

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 names a specific mechanism and resource: ICMP ping, with min/avg/max/mdev statistics, plus a TCP-connect fallback. This distinguishes it in spirit from siblings like net.trace and net.health, but it does not explicitly name or contrast any sibling tool.

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?

There is no guidance on when to use this tool versus net.health, net.trace, net.portcheck, or net.httpcheck. The only implied use is a basic reachability/latency check, but no conditions, exclusions, or alternatives are stated.

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