browser_open_system_page

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

With no annotations, the description carries the full burden. It does disclose one real behavioral trait beyond the schema: 'switch to' indicates it will reuse an existing tab if the page is already open rather than always creating a new one. It says nothing about failure modes for unrecognized page names or any permission/restriction constraints on chrome:// targets.

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?

One sentence, front-loaded with the verb-resource pair followed by the value list. There is no filler and nothing that needs trimming.

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 single-parameter tool with no output schema and no annotations, the description covers what the tool does and which values it accepts. The only meaningful gap is undefined behavior for invalid or unsupported page names.

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% and the schema already documents the single parameter, so the baseline is 3. The description adds genuine value by listing additional valid values not present in the schema ('bookmarks', 'version', 'gpu', 'net-internals'), effectively expanding the accepted enum.

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 gives a specific verb pair ('Open or switch to') and a precise resource ('Chrome system page'), then enumerates the accepted page names. This clearly separates it from browser_navigate, though it never names that sibling explicitly.

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 implied by the enumerated system pages, so an agent can infer this is for chrome:// destinations rather than arbitrary URLs. However, there is no explicit statement of when to prefer this over browser_navigate or browser_list_tabs, and no exclusions are given.

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