Verify Connectivity (Ping Test)

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

readOnlyHint=true is consistent with a pure ping. Beyond the annotation it discloses non-obvious behavior: automatic retry when a destination loses all packets, the ARP/STP reason the first ping often fails, and that raw output is returned only for failures — exactly the facts an agent needs to interpret partial results.

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 behavioral core is front-loaded in the first two sentences and each sentence carries information. The three examples add useful routing cues but make the block longer than strictly necessary for a 3-parameter tool.

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 format need not be explained, and the description covers the remaining gaps: retry semantics, failure-only raw output, and where the ping executes from. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3; the description earns a bump by explaining why the 'attempts' retry parameter exists (fresh switch links and ARP resolution cause first-ping loss) rather than just restating its default. It adds nothing new for 'source' or 'destinations' beyond the schema text.

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 each destination from a device') plus the exact report shape (sent/received/loss per destination). The scope is tight enough that an agent can distinguish it from the nearest sibling, send_simple_pdu, without opening the schema.

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?

Gives concrete invocation scenarios via three examples and frames it as 'the standard way to verify a CCNA lab end to end', which tells the agent when to reach for it. It never states when not to use it or names an explicit alternative such as send_simple_pdu, so it falls short of a 5.

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