browser_get_network_requests

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

With no annotations provided, the description must fully disclose behavioral traits but only offers the word 'buffered,' implying a stored history rather than a live stream. It does not clarify the read-only nature, buffer limits, session requirements, or error behavior, which is a significant omission for a diagnostic tool.

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, well-formed sentence that front-loads the core purpose without redundant words. It is concise, but the extreme brevity leaves necessary details unaddressed, making it efficient yet under-specified.

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 (7 parameters, no output schema, no annotations), the description is woefully incomplete. It does not explain parameter meanings, return data format, or when to use the tool relative to its 18 siblings, so it fails to provide enough context for reliable invocation.

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 description coverage is only 14% (only sessionId has a description), and the tool description fails to add any detail about the seven parameters. The phrase 'diagnostic filters' is too vague to convey the meanings of limit, method, search, status, failedOnly, and resourceType, so it does not compensate for the schema's low coverage.

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 'Query buffered network request history with diagnostic filters' clearly uses a specific verb 'Query' and specifies the resource as 'buffered network request history,' making its purpose understandable. It is somewhat distinguishable from the sibling 'browser_get_failed_requests' (which targets only failed requests), but it does not explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives such as browser_get_failed_requests or browser_get_request_details. There is no mention of appropriate contexts, exclusions, or prerequisites, leaving the agent to infer usage from the tool name alone.

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