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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive). The description still adds real behavioral context: results originate from HackerTarget's probe host rather than the caller's vantage point, and ICMP-blocking hosts produce false 'down' readings. It stops short of rate limits or output-format detail.

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?

Front-loads colloquial query phrasings, then the mechanism, then the usage condition and caveat. Every sentence carries information; nothing is redundant.

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 single-parameter read tool with full schema coverage and annotations, plus a description that names the return values (reachability and RTT), an agent has everything needed to call it correctly and interpret the result, including the false-negative caveat.

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?

Only one parameter with 100% schema description coverage, so the schema already documents 'target' as a hostname or IP. The description reinforces that the target is a host/address but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 a specific verb+resource (ICMP ping a host) plus the mechanism (via HackerTarget) and the exact outputs (reachability, round-trip time). It also frames the resource in the user's own vocabulary ("Is [host] up", "ping [X]"), making it easy to distinguish from path-oriented siblings like mtr or traceroute.

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?

Gives an explicit when-to-use condition: "Use for a liveness check when you cannot ping from where you are." However, it never names the competing alternatives (mtr, traceroute) or when-not to use them, so routing between siblings is left partly to inference.

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