pve_set_node_dns

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Set' implies a write/mutation operation, but the description doesn't specify whether this requires administrative privileges, whether changes are persistent across reboots, potential system impacts, or error conditions. It also doesn't mention that DNS2 and DNS3 are optional parameters (only node and search are required).

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, efficient sentence with zero wasted words. It's appropriately sized for a straightforward configuration tool and gets directly to the point without unnecessary elaboration.

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 system configuration mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what successful execution looks like, whether changes require node restart, potential side effects, or error handling. The agent lacks crucial context for safe and effective use of this tool.

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%, providing clear documentation for all 5 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, such as format examples (e.g., IP addresses for DNS servers) or relationships between parameters. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 'Set node DNS configuration' clearly states the action (set) and target resource (node DNS configuration). It distinguishes from sibling tools like pve_get_node_dns (read) and pve_set_node_time (different configuration type), but doesn't explicitly differentiate from other node configuration tools like pve_set_cluster_firewall_options.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, when DNS configuration should be updated, or what happens after setting (e.g., whether changes take effect immediately). It also doesn't reference the complementary pve_get_node_dns tool for checking current configuration.

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