browse_page

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

With no annotations provided, the description carries the full burden of disclosure. It mentions the use of Playwright and a headless browser, but fails to describe key behaviors such as timeouts, error handling, what each action returns in detail (e.g., screenshot viewport vs full page), or authentication implications.

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 relatively short and front-loaded with the core purpose. The actions are presented in a clear bullet-like list, but the structure could be improved by grouping related information or providing example usage.

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 complexity (multiple actions, 4 parameters, no output schema, and 0% schema coverage), the description is insufficient. It lacks important details like return types for each action, error handling, prerequisite conditions, and constraints on the URL.

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 input schema has 0% description coverage, so the description must compensate. It lists possible action values and hints at the instruction format for click/type, but does not explain the 'api_key' parameter or provide details on how to use each action fully.

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 clearly states that the tool browses a webpage using a headless Chromium browser and lists the available actions. It distinguishes itself from siblings like 'web_search' (which returns search results) by mentioning interactive actions (click, type), but could explicitly say it handles dynamic JavaScript content.

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 does not provide any guidance on when to use this tool over alternatives like 'extract_article' or 'web_search'. It lists actions but does not explain the context in which this tool is preferred (e.g., for interactive pages requiring JS execution).

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