browser_read

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only operation and names the default view, but says nothing about side effects, preconditions (a tab/page must already be open), whether reads are cached/live, or pagination semantics beyond the bare word 'offset'.

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 dense sentences, front-loaded with the core action and immediately followed by the view taxonomy and parameter hints. Every clause carries information, though the telegraphic style trades some readability for brevity.

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 read tool with no annotations, no output schema, and 0% schema description coverage, the definition is only moderately complete. It fails to describe the return shape of each view, what 'refs' are, the 'max' parameter, or the 'changes' view, which an agent would need in order to invoke it confidently.

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 compensate, and it partially does: it explains the view modes, filter, and offset. However it omits 'max' entirely and never mentions the 'changes' enum value present in the schema, leaving one parameter and one enum value undocumented anywhere.

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 specific verb+resource: 'Read the current page.' That is clear and distinguishable from the act/click siblings. It does not explicitly name any sibling (e.g., browser_act, browser_screenshot), so it stops short of the 5-level sibling differentiation.

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 only implied: the view list communicates 'use this to extract content,' and 'Use filter to narrow, offset to page' hints at bulk-reading. There is no explicit when-to-use or when-not, and no mention of alternatives such as browser_act for interaction or browser_screenshot for visuals.

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