Ping Test

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

readOnlyHint=true already declares the safety profile, so the bar is lower; the description still adds real behavioral value by disclosing the empirically observed requirement that all fields be sent and interface be non-empty, plus the exact failure code (3001). It does not state whether the ping is asynchronous or how long results take to appear, but the device-specific quirk is exactly the kind of context annotations cannot carry.

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?

Two short sentences, front-loaded with the action and immediately followed by the critical constraint and the result-reading pointer. No filler; minor density loss from the inline code/backtick formatting.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. Given that, the description supplies the two things an agent most needs: the strict all-fields/interface requirement and where to read results. Only the timing/asynchronous nature of the test is left unstated.

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?

Schema description coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema: the schema marks only host as required, whereas the text states all seven fields must be present and interface must be non-empty or the call fails with 3001. This corrects a misleading impression left by the 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?

States a specific verb and resource (执行 Ping 测试 / execute a ping test) and names the sibling that reads the outcome (ping_result), so an agent can distinguish it from ping_result and other diagnostics like traceroute. It does not explicitly distinguish itself from traceroute/iperf/speed_test, keeping it short of a 5.

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 routes the agent to ping_result for reading results, which implies the intended two-step workflow (start here, read there). However, it gives no guidance on when to prefer ping over traceroute or other connectivity tools, so usage is only implied rather than contrasted.

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