Create ping monitor

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

Discloses that the monitor uses ICMP, reports network-level metrics, and will show as down if ICMP is blocked, providing clear expectations about what the monitor does and its limitations.

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 two sentences, concise, and places the primary purpose first, with usage guidance and caveats following.

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?

Given the simple tool and fully described schema, the description covers purpose, usage, and limitations, making it complete for an agent to decide when and how to use it.

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 schema descriptions already cover the parameters (url, name, isActive, frequency). The tool description does not add specific parameter-level semantics beyond the overall context, so it does not exceed the baseline for high schema coverage.

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?

Clearly states the tool creates a ping monitor for a host using ICMP, reports round-trip time and packet loss, and distinguishes from HTTP monitors by noting it doesn't check services.

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?

Explicitly states when to use (for servers, routers, anything without a web service) and warns about ICMP blocking, which helps decide between ping and other monitor types.

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