browser_network_requests

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

With no annotations, the description carries the burden of behavioral disclosure. While 'Read' implies a non-mutating operation, the tool has a 'clear' parameter that could have side effects, and the description does not disclose whether the buffer is cleared, how results are formatted, or any other behavioral nuances.

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, direct sentence that front-loads the core action and resource. It contains no filler or redundancy, making it a model of conciseness.

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?

The tool lacks an output schema and annotations, so the description should compensate by explaining return values, buffer behavior, and relationship to siblings. It does none of these, leaving the 'clear' parameter and the difference from 'browser_network_request' unexplained.

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 input schema describes two of the three parameters (pageId and sessionId) with descriptions, but the tool description itself adds no parameter semantics. The 'clear' parameter is left undocumented in both the schema and the description, which is a significant gap given it controls potential side effects.

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 the specific verb 'Read' and the resource 'network requests buffered by this automation session,' clearly stating the tool's function. The plural 'requests' and 'buffered' distinguish it from the sibling 'browser_network_request' (singular), which likely performs a single 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?

No guidance is provided on when to use this tool versus alternatives, such as the singular network request tool or other browser inspection tools. There are no mentions of exclusions, alternatives, or ideal usage scenarios, leaving the agent to infer applicability.

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