set_dns

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

No annotations are provided, so the description carries the burden. It states that the tool returns 'Current DNS settings after the change', indicating a mutation with a response. It does not disclose side effects, required permissions, or whether changes are reversible, but it does clarify the behavior of each parameter.

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 well-structured with Args and Returns sections, using clear bullet-style text. It is fairly concise given the number of parameters, though some redundancy exists (e.g., repeating 'block' in each parameter name in the description).

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 tool with 8 parameters and no annotations, the description covers all parameters, their conditions, and the return value. The output schema is present, but the description still clarifies the return behavior. No critical gaps.

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 has 0% description coverage, but the description's Args section explains each parameter's purpose and conditions (e.g., 'servers' only when mode is custom, blocking options only in default mode). This adds critical meaning beyond the schema's type and default values.

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 it 'Configure DNS settings' and distinguishes between 'default' and 'custom' modes, listing specific blocking options. This verb+resource pair is distinct from sibling tools like set_daita or set_killswitch.

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 explains the two modes (default vs custom) and their associated parameters, implying usage contexts. However, it does not explicitly state when to use this tool over alternatives, nor does it provide prerequisites or exclusions.

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