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

The readOnlyHint=true annotation already establishes the safety profile, so the description only needs to add context. It supplies the REST mapping (GET /tailnet/{tailnet}/settings), confirming a pure read of a single tailnet-scoped resource, but says nothing about auth/permission requirements or the shape/size of the returned settings object.

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?

Two short sentences with the core purpose front-loaded and the REST endpoint appended as a compact implementation reference. No filler, no restatement of the title, every clause carries information.

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 with no output schema, the description covers what the tool returns at a category level and how it is invoked. The main residual gap is that the returned settings structure is not characterized at all, which matters slightly since no output schema exists to fill that in.

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 zero parameters, so the baseline is 4 and there are no argument semantics to add. The description's mention of {tailnet} in the endpoint path implies a tailnet-scoping context that the empty schema does not express, which is a small bonus but not a substitute for real parameter documentation.

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 (Get) and resource (the tailnet's settings), and the parenthetical enumeration of setting categories (device approval, key expiry, posture) tells the agent this is broader than the narrower tailnet-scoped siblings like tailscale_get_dns_preferences or tailscale_get_policy_file. It stops short of explicitly naming those siblings, so it is clear but not maximally differentiated.

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 explicit when-to-use statement, prerequisite, or named alternative. Usage is only implied by the scope hint ('the tailnet's settings') and the enumerated categories, which lets an agent infer this is the tool for tailnet-wide policy/approval configuration rather than device or DNS lookups, but nothing is stated outright.

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