ping

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the concrete output ('public IP address') without contradicting the annotation. It doesn't discuss response format or latency, but for a simple ping utility the disclosure is adequate.

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, self-contained sentence with no filler. It efficiently front-loads the core purpose and provides no extraneous information.

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?

With no parameters, an output schema present, and a readOnly annotation, the one-sentence description fully covers the tool's behavior for the agent. Nothing further is needed.

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?

This tool has zero parameters, so the description carries no burden for parameter documentation. The baseline of 4 applies because there is nothing to explain beyond what is already evident from the empty schema.

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 uses a specific verb ('Test') and clearly identifies the resource ('API connectivity') while also noting the additional output of the public IP. This distinguishes it sharply from the sibling DNS and domain management tools.

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 clearly implies its use case—checking API connectivity and retrieving the public IP. It doesn't explicitly enumerate alternatives or exclusions, but given the tool's simplicity and the obvious distinction from the sibling domain-management tools, the context is sufficiently clear.

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