update_system_dns

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

The description provides no behavioral detail beyond the action itself. Annotations indicate readOnly=false, idempotent=true, and destructive=false, but the description does not add context about side effects (e.g., service restart, persistence, or relationship to apply_immediately).

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, direct sentence with no filler. It is front-loaded with the core action and resource, and every word adds value.

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?

Although the description is minimal, the combination of full schema coverage, output schema, and annotations (idempotent, non-destructive) provides sufficient context for an agent to invoke the tool correctly. Some additional context about applying changes could be useful, but not necessary given the structured data.

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 input schema describes all three parameters with complete coverage (dnsserver, dnslocalhost, apply_immediately). The description adds no additional parameter semantics, so it earns the baseline score of 3 for good schema coverage.

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 updates system DNS server settings, using a specific verb and resource. It distinguishes from sibling getters like get_system_dns and other DNS tools by focusing on the system-wide DNS server configuration.

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 offers no guidance on when to use this tool versus alternatives such as update_dns_resolver_settings or get_system_dns. It lacks context about prerequisites, exclusions, or scenario-based recommendations.

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