set_dns_servers

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

Without annotations, the description carries full burden and does disclose the write authorization requirement. However, it lacks details on whether the change is immediate, persistent, or requires a reboot, which are typical behavioral traits for a router configuration tool.

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 short but grammatically awkward ('Set server DNS upstream router') and mixes languages. It covers essentials but could be more polished and front-loaded with the main action.

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?

Given no annotations, no output schema, and 2 parameters, the description explains the parameters and a prerequisite. However, it misses behavioral context (e.g., what happens to existing DNS servers, immediate persistence). Adequate but not complete for a configuration 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?

With 0% schema description coverage, the description adds valuable meaning: it gives format and example for 'servers' and explains the purpose of 'allow_remote_requests' (making the router a LAN DNS resolver). This goes significantly beyond the raw schema.

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 'Set server DNS upstream router', clearly indicating it configures the upstream DNS servers. However, it does not explicitly distinguish from sibling tools like dns_settings or dns_static, making the purpose slightly less sharp.

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 only specifies a prerequisite environment variable (BUTUH MIKROCLAW_ALLOW_WRITE=true) but provides no guidance on when to use this tool versus alternatives like dns_settings or add_dns_static.

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