tailscale_set_dns_configuration

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

Annotations already signal destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds valuable context by specifying exactly what gets overwritten—'nameservers, search paths, split DNS, MagicDNS preference'—going beyond the generic destructive annotation.

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 compact sentences front-load the verb and resource, then state the effect. There is no redundancy, and every word 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?

The description plus schema covers the atomic replacement behavior, the four parameter groups, and the nested splitDns structure. It does not explicitly state the effect of omitting a parameter (e.g., cleared vs. left unchanged), but 'Replaces all DNS settings' strongly implies full replacement.

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%, so the baseline is 3. The description maps the four parameter groups (dns, searchPaths, splitDns, magicDNS) to 'nameservers, search paths, split DNS, MagicDNS preference' but does not add syntax, defaults, or behavior beyond what the schema already documents.

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 the specific verb 'Set', the resource 'unified DNS configuration for your tailnet', and the qualifier 'in a single call'. It then enumerates what is replaced, which clearly distinguishes it from sibling tools like tailscale_set_nameservers, tailscale_set_search_paths, and tailscale_set_dns_preferences.

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 phrase 'in a single call' and 'Replaces all DNS settings' clearly conveys this is the comprehensive DNS configuration endpoint, contrasting with the piecemeal setter siblings. It does not explicitly name when-not-to-use or list alternatives, but the unified-vs-specific context is strong and easily inferred.

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