ping_host

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

With no annotations, the description carries full burden. It discloses that it uses the system ping binary unprivileged, works on macOS/Linux, validates input strictly, clamps count to 1-10, and outlines return shapes. Minor omission: no mention of ICMP blocking or permission variability.

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 front-loaded with the core purpose and efficiently structured with Args/Returns sections. Every sentence adds value, though the first two sentences could be merged without loss.

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 simple 2-parameter tool with an output schema present, the description covers purpose, parameters, return values, platform constraints, and input validation. It lacks mention of rate limiting or ICMP-specific failure modes, but overall it is thorough.

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%, but the description fully compensates by explaining each parameter with examples, validation rules, and clamping behavior. For 'host', it specifies valid formats and rejection of shell metacharacters; for 'count', it states default and bounds.

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 'Ping a host with ICMP echo requests and report packet loss and latency' and answers a specific question. This verb+resource combination distinguishes it from sibling tools like dns_lookup, http_health, and traceroute_host.

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 description provides a clear use case ('Is this machine reachable at the network level?') but does not explicitly guide the agent on when not to use this tool or which sibling to choose instead. Alternatives are implied but not contrasted.

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