Network conditions check

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so 'Read-only' is largely redundant. The description does add value beyond annotations by disclosing the return format ('Returns JSON') and the categories of data returned, which matters since there is no output schema, but it says nothing about execution cost, runtime, or whether it contacts external relays.

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 compact sentence, front-loaded with the action and resource, followed by two short factual clauses. Nothing is padded and every element (diagnostic list, return format, safety) earns its place.

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 zero-parameter, non-destructive diagnostic whose safety profile is fully covered by annotations, the description supplies the key missing pieces: what is measured and that JSON comes back. It stops short of describing the JSON shape or typical latency of the check, but nothing essential to invoking it correctly is absent.

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 no parameters and the schema is empty, so there are no parameter semantics to explain. Per the baseline for zero-parameter tools, a 4 is appropriate.

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 ('Analyze') and resource ('local network conditions'), then enumerates the concrete diagnostics it surfaces: DERP relay reachability & latency, NAT type, UDP, IPv6. That is enough to separate it from siblings like tailscale_status or tailscale_ping, though no sibling is named explicitly, which keeps 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?

Usage is implied by the content ('analyze network conditions') but the description never says when to reach for this versus tailscale_ping, tailscale_dns_status, or tailscale_status, and gives no preconditions or exclusions. Adequate for a read-only diagnostic but leaves routing to inference.

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