Read the current page

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

readOnlyHint=true already covers the safety profile, so the description's extra value is the disclosed return contents and the '(capped)' truncation warning, which is genuine behavioral context an annotation cannot carry. It does not explain what happens to content beyond the cap (silent truncation vs. error) or how the cap is set, leaving one meaningful gap.

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 short sentences: the return contents are front-loaded, and the comparison to screenshots follows as supporting rationale. No filler and nothing redundant.

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 usefully enumerates the returned fields, which is the right coverage. However, for a tool whose only parameter governs truncation, the missing explanation of the cap and its default leaves the definition incomplete for correct invocation.

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?

The single max_chars parameter has 0% schema description coverage (no description, only default 12000 / min 500 / max 50000), so the description must compensate. '(capped)' gestures at truncation but never names the parameter, its unit, its default, or that the cap is configurable — an agent cannot connect the behavior to the knob.

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 enumerates exactly what the tool returns (title, URL, selected text, readable text of the active tab), which identifies the resource and scope clearly alongside the verb in the name/title. It also differentiates against one sibling (screenshot) with 'faster and more exact than a screenshot', though it never names or contrasts against browser_elements, look, or the other page-reading alternatives.

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?

'Faster and more exact than a screenshot' implies a when-to-use preference over screenshot tools, so usage is implied rather than stated. There is no explicit condition, no when-not guidance (e.g. use browser_elements for structured DOM), and no mention of the active-tab prerequisite that selects this over browser_tabs or browser_switch_tab.

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