Stop Ping

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

With no annotations, the description carries the full behavioral burden but discloses nothing beyond the literal action. It does not say whether the in-flight results are discarded or remain retrievable via ping_result, whether the call is idempotent when no ping is running, or whether it targets a single global ping session (implied by zero parameters).

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 single four-word phrase is front-loaded and free of waste, which is appropriate for a trivial action. However, it is so terse that it borders on under-specification rather than disciplined conciseness.

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. Still, for a state-changing stop command with no annotations the description omits essential context: what exactly is terminated, whether results survive the stop, and how it relates to stop_traceroute. It is not complete enough to call confidently.

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 for the description to clarify; the baseline for a no-parameter tool is 4. The empty schema with additionalProperties:false is consistent with a single-session stop action.

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 测试' = stop the Ping test), so the agent knows exactly what action is performed. It does not, however, distinguish itself from the closely related sibling stop_traceroute, leaving the agent to infer the boundary from the name alone.

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 gives no when-to-use context, no prerequisite (e.g. a ping must be running), and no mention of alternatives like stop_traceroute or the ping_test/ping_result siblings. Usage is only implied by the verb.

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