browser_read

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

Annotations already provide safety hints (read-only, idempotent, non-destructive). The description adds context by mentioning the 'real Chrome session' and 'public HTTP(S)' scope, which tells the agent about the environment and what URLs are acceptable. This goes beyond the annotations.

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?

The description is a single, well-structured sentence that front-loads the action and then lists extraction modes. It contains no redundant words or filler.

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?

Given the tool's simplicity, the presence of an output schema, and strong annotations, this description is complete. It covers the purpose, the extraction outputs, and the scope without needing to describe return values.

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. It explains the extract parameter by mapping it to concrete output types (readability, text, HTML, XHR), which adds value beyond the schema. However, wait_ms and max_chars are not described and rely solely on their self-explanatory names.

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 uses specific verbs ('load', 'extract') and identifies a clear resource: a public HTTP(S) URL in the user's real Chrome session. It also enumerates the extraction modes (readability text, visible text, rendered HTML, XHR responses), which effectively distinguishes it from sibling tools like browser_read_page or browser_snapshot.

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?

The description implies usage for loading public URLs and extracting page content, giving clear context. However, it does not explicitly state when not to use this tool or name alternatives, such as browser_read_page for the current page.

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