Ping Result

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

The readOnlyHint=true annotation already establishes this is a safe read. The description adds nothing beyond that — it doesn't say whether results are only available after a completed test, whether they persist, or how they relate to stop_ping.

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 phrase with no waste, appropriately terse for a zero-parameter read tool. It is efficient rather than padded, though it stops short of carrying any real 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 an output schema present, return values need not be explained, and there are no parameters to document. The missing piece is the workflow context — that ping_test must run first and how this pairs with stop_ping/traceroute_result — which an agent calling blind would lack.

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, which is the baseline-4 case; there is nothing for the description to disambiguate and the empty schema fully covers the interface.

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?

States a specific verb and resource ('读取 Ping 测试结果'), making it clear this retrieves results rather than initiating (ping_test) or halting (stop_ping) a test. However, it never names or contrasts those siblings, so the differentiation is only inferable from the verb choice.

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?

No when-to-use guidance, no prerequisites, and no mention of the related tools (ping_test, stop_ping, traceroute_result). The agent must infer that a ping test has to be started before results can be read.

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