Open one of Firefox internal about: pages

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

The description usefully discloses the side effect (a new tab is created, consistent with readOnlyHint=false) and adds a real behavioral note that these pages "render real content this way." However, "any other whitelisted about: name" is vague about what the whitelist is, and the MEASURED/internal-menu framing is noise rather than operational detail.

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 purpose is front-loaded in the first sentence, which is good, but the rest rambles through menu provenance and "MEASURED" evidence that does not help an agent call the tool. The awkward clause "netmonitor-free pages" adds confusion rather than information.

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 two-parameter tool with full schema coverage and no output schema, the description covers purpose and the new-tab side effect adequately. It falls short on the whitelist ambiguity and says nothing about failure when a page cannot be opened.

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% with an enum of 15 page names, so the schema already carries the parameter meaning. The description names a few pages but also claims it accepts "any other whitelisted about: name," which conflicts with the closed enum and could lead an agent to pass an invalid value.

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?

"Open a Firefox internal page in a new tab" gives a specific verb plus resource, and the contrast with "DevTools APIs" separates it from browser_devtools_open and browser_navigate. What it lacks is an explicit naming of the sibling an agent should pick instead, so the differentiation is inferential.

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 phrase "rather than DevTools APIs" implies the DevTools tools cover the non-about: entries, but no alternative is named and no positive/negative conditions are stated outright. An agent can infer the split, but must know the sibling list to act on it.

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