Configure DNS over HTTPS

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

Annotations already flag this as a mutating, destructive write, and the description correctly identifies the persisted prefs being overwritten. However, it adds no context on the practical consequence — that a bad DoH mode can break DNS resolution or that the change persists beyond the session — which is exactly what an agent needs for a destructiveHint=true network setting.

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?

Two sentences, no filler, with the concrete prefs and enum mapping front-loaded before the UI-equivalence framing.

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 2-parameter setter with no output schema, the description covers what is written and the mode encoding, but omits when the change takes effect and what interacts with it (e.g. the existing resolved DNS state). Adequate, not complete.

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 coverage is 100%, so the baseline is 3, but the description earns above baseline by mapping each human-readable enum label to the raw integer value actually written (0/2/3/5), which the schema does not reveal. It says nothing extra about the uri parameter beyond the schema's own example.

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?

States a specific verb ('Set') against a specific resource (network.trr.mode and network.trr.uri), and grounds it in the visible UI control (Network Settings > DNS over HTTPS). It does not distinguish itself from the generic sibling browser_set_pref, which could write the same prefs, so it stops short of a 5.

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?

Usage is only implied via the UI equivalence sentence; there is no explicit when-to-use, no mention that browser_set_pref is an alternative for the same underlying prefs, and no note about whether a restart or reload is required.

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