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

Annotations already declare readOnlyHint=true, so the safe-read nature is established. The description adds contextual detail about the specific settings returned and the REST endpoint, but doesn't disclose response format or pagination. It provides some value beyond annotations but not extensive behavioral detail.

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 description is a single, well-formed sentence that directly states the purpose and gives a relevant REST endpoint. It is concise with no wasted words, perfectly sized for the tool's simplicity.

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, read-only getter, the description sufficiently covers what the tool does and what it returns (tailnet settings with examples). The absence of an output schema is not a gap because the description provides enough information about the response nature. The tool is simple enough that the description is complete.

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?

There are no parameters, so the description has no need to elaborate on parameter semantics. The schema coverage is 100% (vacuously), and the description adds no conflicting or confusing information. Baseline of 4 is appropriate for a zero-parameter tool.

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 clearly states the tool's function with a specific verb ('Get') and resource ('tailnet's settings'), listing example settings (device approval, key expiry, posture). This distinguishes it from sibling tools that target other resources like devices, users, or DNS.

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 description provides clear context by naming the specific resource ('tailnet settings') and even referencing the REST endpoint. Although it does not explicitly mention when not to use it or name alternatives, the scope is self-evident given the sibling tools, making usage conditions clear enough.

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