net.httpcheck

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

With no annotations the description carries the full burden. It does disclose the return contents (timing breakdown, headers, size) and signals a safety posture via 'LAN-safe', but leaves redirect handling, error/timeout behavior, and what 'LAN-safe' actually means undefined.

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 dense line with the payload (methods, outputs) front-loaded and zero filler. The telegraphic fragment style trades some readability for compactness, but no sentence is wasted.

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 3-parameter, annotation-free tool with no output schema, the description is too thin: it does not explain timeout effects, failure modes, or whether redirects are followed, all of which an agent needs before choosing it over net.ping or net.health.

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%, so the schema documents only types, defaults and enum values. The description echoes the GET/HEAD method values but says nothing about url format expectations or the 1s-30s timeoutMs range and what happens when it elapses.

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?

States the resource and method (HTTP GET/HEAD) and enumerates the results it returns (timing split dns/connect/ttfb/total, status, headers, size), which lets an agent separate it from ICMP/TCP siblings like net.ping or net.portcheck. It never names a sibling explicitly, so differentiation is inferential rather than stated.

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 when-to-use or when-not-to-use guidance and no pointer to an alternative such as net.ssl, net.health or sec.exposure. The only contextual hint is the trailing phrase 'LAN-safe', which gestures at suitable environments without explaining the criterion.

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