ping

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

With no annotations, the description carries the full burden. It discloses the exact output format and the health-check nature of the operation. It does not explicitly state 'no side effects,' but the minimal ping semantics make that reasonably clear.

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 concise and well-structured: a one-line label, a return contract, and an example. There is no filler, and the most important information appears first.

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 zero-argument reachability check with an output schema, this description is fully sufficient. It states what the tool does, what it returns, and how to call 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 tool has zero parameters and the schema already confirms an empty parameter object, so the schema description coverage is effectively 100%. Per the baseline for zero-parameter tools, a 4 is appropriate; no additional parameter explanation is needed.

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 explicitly identifies it as a health-check tool and gives the exact return payload, so an agent immediately knows its purpose. It is clearly distinguishable from the geospatial sibling tools by being a reachability probe rather than a geocoding/isochrone/POI operation.

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 states that it is for 'any MCP client to confirm reachability,' which gives a clear usage context. It does not enumerate exclusions, but none are really needed because the tool takes no arguments and the sibling tools serve obviously different purposes.

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