nex_browser_network_request

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

The annotation readOnlyHint=true already covers safety. The description adds the fact that the request is 'buffered' and uses 1-based indexing, but it does not explain how the buffer is populated, whether requests are captured by default, or what happens for out-of-range indices.

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, concise sentence that immediately conveys the action, target, and indexing scheme. No filler words; every element earns its place.

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 lack of an output schema, the description should hint at the return format, but it does not. It also omits any mention of prerequisites (e.g., whether the browser session must be in a network-recording state). For a simple read tool, this is a moderate gap.

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 description explicitly states that the required 'index' is 1-based, which adds crucial meaning beyond the schema's minimum of 1 (which does not imply 1-based). The other parameters are already described in the schema, so this targeted addition is valuable.

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 ('Read') and resource ('buffered network request') and clarifies the access method ('by its 1-based index'). This clearly distinguishes it from the sibling tool 'nex_browser_network_requests' which lists all requests.

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?

No guidance is given on when to use this tool versus the plural 'nex_browser_network_requests'. The description does not mention that one might first list requests to get an index, which is a natural workflow and important for effective usage.

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