Read the page

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

Annotations already cover read-only and open-world, so the bar is lower, and the description adds real value: the call bumps an observation number while keeping the same indexed action space, meaning prior references stay valid. It doesn't explain what happens if nothing changed or whether any latency/limit applies.

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, front-loaded with what it does, then when to use it. Every clause carries information; nothing is padding.

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 supplies the essential return semantics (new observation number, same action space), which is what an agent most needs. Missing only edge-case behavior such as whether a re-read triggers navigation or waiting.

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?

Zero parameters, so the baseline is 4. The description correctly frames this as a parameterless re-observation, and the empty schema is consistent with that.

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 action and resource ('Read the current page again') and clarifies the result is the same indexed action space under a new observation number, which separates it from browser_act or browser_screenshot. It doesn't name those siblings explicitly, so the differentiation is implied rather than stated.

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 two concrete triggers: the page changed on its own, or an action was refused. That is actionable guidance, though it doesn't state exclusions (e.g. use browser_screenshot when you need pixels, or browser_act when you want to act rather than observe).

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