Ping

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

No annotations are provided, so the description carries the full burden. It does disclose the observable behavior ('returns pong'), which is the key trait for a probe, but it does not state that the call is side-effect free, idempotent, or whether it requires a running server.

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 short sentence states purpose and expected result with zero filler, and the key information is front-loaded.

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 trivial probe with an output schema already describing the return payload, the description is nearly sufficient. The only gap is the lack of any hint about when this is preferable to server_status or runtime_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 zero parameters, so there is nothing to document; the baseline for a no-parameter tool is 4. No parameter meaning is missing or ambiguous.

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 names a specific action and outcome: a connectivity test that returns 'pong'. It is unambiguous what the tool does, though it never distinguishes itself from siblings like runtime_info or server_status that could also confirm the server is alive.

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 implied by the well-known 'ping' idiom and the phrase '连通性测试', so an agent can infer it is for reachability checks. However, there is no explicit when-to-use guidance and no comparison against alternatives such as server_status.

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