browser_list_network_requests

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

With no annotations, the description carries the full burden, but it does disclose one genuinely useful trait: it reads in-memory captured data and does not call Chrome, implying results depend on a prior capture and carry no live-browser cost. It omits prerequisites (active session/capture), pagination defaults and 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?

A single compact sentence with no filler, and the important constraint (in-memory, no Chrome call) is front-loaded. The terseness is efficient, though it borders on under-specification.

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 4-parameter, no-annotation, no-output-schema tool with zero schema coverage, this is not enough. The description never says what fields come back, that a session/capture must exist, or how limit/offset behave, so an agent lacks what it needs to call it confidently.

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?

Four parameters with 0% schema description coverage, and the description mentions none of them. session_id, limit, offset and resource_type are completely undocumented in both places, leaving the agent to guess valid values and semantics.

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 name supplies the verb+resource (list network requests), but the description itself only says it queries 'network metadata', which is vaguer than the tool name. The scoping clause ('captured ... in memory') is the only real distinguishing content, and it does not explicitly contrast with sibling browser_get_network_request.

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?

Nothing states when to use this rather than browser_get_network_request (single request) or when a capture must already be running via browser_start_capture. Usage is only inferable from the name and sibling set.

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