Ping from the router

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds that execution originates on the router rather than the MCP host, which is genuinely useful context, but it says nothing about timeouts, likely latency or packet-loss results, or how the default count of 4 is applied.

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 tight sentence with the core action front-loaded and the parenthetical earning its place by adding usage context. Nothing is repeated from the title or restated without value.

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 6-parameter diagnostic tool with no output schema and no return-value documentation, the description should say what comes back (latency, loss, per-packet results) and how the device default is resolved. It covers the core action adequately but leaves an agent guessing about results and several parameters.

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 only 33% — address, interface, srcAddress, and count are undocumented in the schema. The description partially compensates by surfacing the interface and source-address concepts, hinting at what those two parameters do, but leaves count and address semantics unaddressed, so it is a partial rather than complete compensation.

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 a host') and disambiguates direction by saying 'from the router itself', which separates it from pinging the router. It does not name the nearest sibling (mikrotik_traceroute), so it falls short of full sibling differentiation.

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 parenthetical gives a positive use case ('test connectivity from a specific interface or source address'), which is real guidance. However, it offers no exclusions and no mention of the obvious alternative, mikrotik_traceroute, for path diagnosis rather than reachability.

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