Tailscale status (this host)

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real value: it defines exactly when 'connected' is true (BackendState=Running AND Self.Online), warns that a persistent Tailscale IP does not imply connectivity, and notes the plain-status exit code is intentionally ignored. It omits auth requirements or rate limits, but the semantic caveats are genuinely useful.

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?

Front-loaded with the core purpose, and each subsequent sentence addresses a real pitfall (connected semantics, IP persistence, exit code). Dense but nearly every clause earns its place; only the exit-code note is arguably marginal.

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 read-only status tool with a full output schema, the description is more than sufficient, even pre-explaining the normalized 'state' and 'connected' output semantics. Nothing an agent needs to call or interpret it 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 description coverage is 100% with a single well-documented 'peers' boolean, so the schema already carries parameter meaning. The description adds nothing about the parameter, making the baseline 3 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?

States a specific verb ('Report') and resource ('this host's Tailscale connection state'), with the scope 'this host' distinguishing it from sibling tools like tailscale_whoami or tailscale_netcheck. An agent can tell what it returns 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?

The 'this host' scope implicitly narrows it relative to peers/host-oriented siblings, but there is no explicit when-to-use statement or named alternative. Usage is inferable from the scope rather than spelled out.

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