browser_extract

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

No annotations are provided, so the description carries the burden. It discloses that the tool reads from the DOM and can return categorized structured data, which implies a non-mutating extraction. However, it does not describe response shape, limits, or behavior on dynamic or incomplete page content.

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?

A single front-loaded sentence with no filler. 'Pull structured page data from the DOM' communicates the core action, and the colon-delimited list adds helpful mode variety without bloat.

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 and no annotations, the description should explain return values and exact accepted modes. It lists mode-like categories but omits details such as what 'main' returns, whether the output is JSON/text, and whether extraction waits for page readiness. This leaves meaningful gaps for an agent invoking the tool.

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 schema has only a bare 'mode' string with no enum or description (0% coverage). The description compensates by listing candidate modes (text, elements, links, tables, main), but it does not explicitly define them or confirm they are valid values for the mode parameter.

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 a specific verb ('Pull') and resource ('structured page data from the DOM') and enumerates content categories: text, elements, links, tables, or main. It is not explicitly differentiated from browser_observe/browser_search, but the DOM/structured extraction framing gives clear purpose.

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?

There is no guidance on when to use browser_extract versus siblings like browser_observe or browser_search, nor any exclusions. The description solely states what it does, leaving selection entirely to inference.

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