Look at the page (Pro)

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

readOnlyHint already covers the safety profile, and the description adds genuinely new context beyond annotations: the token cost profile, the fact that a separate vision model does the looking, and the client-compatibility constraint. It stops short of saying how long the call takes or whether it waits for page load, which matters for a remote-vision round trip.

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 dense sentence that front-loads the mechanism, then the two usage modes, then the cost and compatibility rationale. Nothing is redundant with the title, and every clause adds 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 correctly establishes that the return value is a text answer. For a two-parameter read-only tool that is nearly enough; only the tabId targeting behavior and any blocking/latency expectation are absent.

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 0%, so the description must carry the parameters. It does clarify the 'question' parameter's two modes (omitted = describe the page, supplied = answer about what is visible), but 'tabId' is never mentioned, leaving the agent unsure which tab is targeted or what the default is.

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?

A specific verb and mechanism: a vision model inspects the rendered page and returns a text answer, either a description or an answer to a supplied question. The 'text instead of an image' framing implicitly distinguishes it from browser_screenshot and browser_read, but no sibling is named outright, leaving the agent to infer the routing.

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 selecting condition: use it when the client cannot display images, or when a textual answer is enough and you want to spend a few hundred tokens rather than an image. It does not state when-not to use it or name browser_screenshot/browser_inspect as the alternatives, so the routing is implied rather than explicit.

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