ping

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

No annotations are provided, but the tool is a zero-parameter read-only probe, so there is very little behavioral surface to disclose. The description confirms it is a non-mutating health check, but says nothing about failure semantics (e.g., what an unhealthy response looks like), which would be the only meaningful added context.

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 front-loaded sentence with zero filler, appropriately sized for a trivial diagnostic tool. Every word earns its place.

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 an output schema present, the return shape need not be described, and with no parameters there is little else to cover. The only gap is the absence of guidance on how this differs from server_info.

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 takes no parameters, so the baseline is 4. There is no parameter meaning for the description to clarify, and the empty schema is self-explanatory.

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?

"Health check for this wrapper server" states a specific diagnostic function and its target (the wrapper server), so an agent knows exactly what it does. It does not, however, distinguish itself from the sibling server_info, which an agent could reasonably mistake for the same purpose.

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?

Usage is only implied: a health check is conventionally used to verify connectivity/liveness before other calls. No explicit when-to-use, when-not-to-use, or comparison against server_info is given, leaving the agent to infer the distinction.

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