Inspect or change the DevTools remote debugging server settings

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

Annotations only give readOnlyHint=false, so the description carries the burden and does add real context: the exact pref name, an observed value, the server module path, and the crucial note that this pref is distinct from the BiDi flag DSH uses. It stops short of saying whether enable/disable takes effect immediately or requires a browser restart.

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?

Front-loaded with the purpose, but the evidence dump ('MEASURED on Firefox Developer Edition... an object, so this build does ship a DevTools server') is diagnostic noise for an invoking agent. The one genuinely load-bearing sentence is the BiDi-flag caveat at the end.

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?

There is no output schema, so the description should say what a 'status' call returns and whether pref changes require a restart — neither is covered. For a two-parameter, no-output-schema tool it is adequate but leaves the operational consequences of enable/disable unexplained.

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% and the action enum is self-documenting ('status = read only; enable/disable flips the prefs'), so baseline 3 applies. The description adds only the mapping of the port parameter to devtools.debugger.remote-port, with no further detail on default/retention behavior.

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 pair (report or change) plus the exact resource (Firefox remote debugging settings, i.e. the Browser Tools > Remote Debugging entry) and even names the underlying pref. It does not explicitly distinguish itself from siblings that could touch the same pref (browser_get_pref/browser_set_pref) or from browser_devtools_open/close, so a small ambiguity remains.

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 clarifies an important scope boundary — DSH's own WebDriver BiDi connection uses a separate --remote-debugging-port flag, not this pref — which helps avoid confusion. But it never says when to prefer this tool over browser_get_pref/browser_set_pref for the same pref, nor any prerequisites (e.g. whether a restart is needed). Usage is only implied.

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