scraping_browser_network_requests

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context by naming the return fields (HTTP method, URL, status code, status text), which compensates for the missing output schema, but says nothing about capture scope, whether the list resets on navigation, or size limits.

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?

Three short sentences with zero filler: purpose first, return contents second, use cases last. Front-loaded and every sentence carries information.

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 input params and no output schema, the description covers the essential contract: what is returned and for what window. Minor gaps remain around capture behavior across navigations and result size, but an agent has enough to call it correctly.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter semantics gap for the description to fill. Nothing extra is needed or provided here.

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 (Get) and resource (network requests) with a clear temporal scope ('since loading the current page'), which separates it from siblings like scraping_browser_get_html or scraping_browser_snapshot that return page content rather than traffic. It does not explicitly name a sibling it supersedes, so it stops short of a 5.

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?

'Useful for debugging API calls, tracking data fetching, and understanding page behavior' implies scenarios but never states when to prefer this over scraping_browser_get_html, get_text, or snapshot. No exclusions or prerequisites (e.g., page must already be navigated). Usage is only inferred.

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