browser_api_request

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

With no annotations, the description carries the full burden. It discloses the session-reuse behavior and return values, but it does not mention that POST/PUT/DELETE requests may cause side effects on the target server, nor does it address redirects, error handling, or whether the request executes within the browser page context.

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 sentences, front-loaded with the core action and key behavioral trait, followed by return value. No filler or redundancy.

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 6-parameter HTTP tool with no output schema and no annotations, the description covers the essential return values and the unique session-reuse aspect, but it omits prerequisites (e.g., browser must be started), default method behavior, redirect handling, and side-effect warnings for mutating methods. These gaps make it incomplete for an agent deciding how to call it safely.

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 50%: url, method, and timeout lack descriptions, though url and method are self-evident. The description adds session-context value (why cookies/storage are reused), but it does not explain the timeout semantics or specify a default method when omitted. It only partially compensates for the schema gaps.

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 states a specific action ('Make an HTTP request') plus a distinctive resource/context ('reusing the browser session's cookies/storage'), and it mentions the return payload (status, headers, body). This clearly differentiates it from navigation, network-log inspection, and cookie-management siblings.

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 gives a clear use case: authenticated API calls without re-login. It implies when this tool is appropriate, but it does not explicitly name alternatives or say when not to use it (e.g., versus browser_evaluate or browser_navigate).

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