Read the text content of an opened about: page

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

Adds genuinely useful measured behavior beyond readOnlyHint: about:processes renders asynchronously and may need a repeat call. It does not describe what happens when no matching about: page is open or how maxChars truncation manifests, which would round out the picture.

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 tight sentences: the purpose first, then the empirically measured caveat. Nothing is repeated from the annotations or schema, and every clause carries 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?

With no output schema, the description does name the return content (title and visible text), and the async caveat covers the main failure mode. Edge cases such as an unopened or non-matching about: page are left unaddressed.

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%, so both page and maxChars are already documented with examples and bounds. The description's "visible text" wording mildly reinforces what maxChars controls but adds no format or syntax detail beyond the schema.

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 concrete verb and resource (report the title and visible text of an about: page) and the qualifier "already-open" implicitly separates it from browser_open_about_page. An agent can immediately tell this reads an existing page rather than creating one.

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?

Gives a clear usage motive (confirm the internal page actually rendered rather than assuming) plus retry guidance after a short wait. It lacks an explicit "do not use for" clause or a naming of alternatives, but the context is unambiguous.

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