restart_dns

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

The description discloses that the tool restarts the DNS resolver, implying a service disruption, but does not provide details on downtime, safety, or prerequisites. Since no annotations are provided, the description carries the full burden, and more behavioral context (e.g., 'This will temporarily disrupt DNS resolution') would be helpful.

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 consists of two short, front-loaded sentences that convey the purpose and usage without any extraneous information. Every sentence 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?

Given the tool's simplicity (no parameters, straightforward action), the description is largely complete. However, the output schema is indicated as existing but not shown; the description could mention what the response indicates (e.g., success message), but this is a minor gap.

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 no parameters and schema description coverage is 100%. The description adds no parameter information, which is acceptable as there are none. Baseline 4 is appropriate for zero-parameter tools.

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 'Restart the Pi-hole DNS resolver' which clearly identifies the action (restart) and the resource (DNS resolver). This verb+resource pair is specific and distinguishes it from sibling tools that perform add, get, remove, or update operations.

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?

It explicitly says 'Use after configuration changes that require a DNS restart,' providing clear context for when to invoke the tool. No exclusions or alternatives are mentioned, but the guidance is sufficient for the tool's purpose.

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