Tailscale ping

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered before the description starts. The description does add one genuine behavioral detail — that the result reports the connection path (DERP relay vs direct) — but says nothing about how `count`/`untilDirect` interact, latency expectations, or failure behavior.

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 sentence that front-loads the action, the peer target, and the diagnostic payoff, with zero filler. Nothing is repeated or padding.

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 all three parameters fully specified in the schema and the safety profile carried by annotations, an agent has nearly everything it needs; the description usefully signals the return content despite no output schema. It would be stronger if it noted the tool's relationship to netcheck and typical latency of a ping.

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%, and each parameter (target, count, untilDirect) is documented in the schema with defaults and bounds. The description adds no syntax, format, or interpretation detail beyond that, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Ping a peer at the Tailscale layer') and even cites the underlying command (`tailscale ping`), plus the key output (DERP relay vs direct path). It does not explicitly contrast itself with the nearest diagnostic sibling, `tailscale_netcheck`, 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?

There is no statement of when to reach for this tool versus `tailscale_netcheck`, `tailscale_status`, or `tailscale_whois`, nor any prerequisites (e.g., peer must be online/authorized). The only guidance is the appended 'Read-only', which restates the annotations rather than advising usage.

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