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

The description goes beyond the annotation bounds by explaining the scope of what a ping reports (network reachability only), clarifying that a host can ping while a web server is down, and revealing that providers blocking ICMP cause monitors to show 'down'. These failure-behaviors are concrete and useful.

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?

Three sentences deliver the core action, use cases, and limitations without redundant words. Each sentence adds distinct information, though the sentence listing use cases and the sentence on service status could be more tightly merged.

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?

The description fully accounts around when to choose ping vs. other personal agents and identifies real-world failure modes. Since an output schema is present, the absence of response field details is acceptable; the description lacks only an explicit pointer to the service-monitor sub-tools.

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?

The input schema already covers all four parameters with rich, specific descriptions (e.g., URL no scheme/port, frequency range, name max length, isActive default). The tool description does not add new parameter-level semantics beyond the schema, so the baseline coverage score 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?

The description opens with a specific action and resource: 'Watch a host with ICMP ping' plus the exact metrics reported (round-trip time, packet loss). It clearly differentiates from service-level by stating it only checks machine reachability, distinguishing it from HTTP, port, and API monitor siblings.

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?

It explicitly says when to use the tool: 'servers, routers and anything with no web service on top,' and warns that it reveals nothing about whether a hosted service is working. The ICMP-blocking provider caveat also sets correct expectations for when the monitor may misreport.

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