browser_network_requests

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention side effects (e.g., replaying requests may cause duplicate submissions), whether authentication is needed, or any rate limits. The description only states high-level functionality without revealing behavioral traits.

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, front-loaded sentence that communicates the core purpose and key feature without unnecessary fluff. It is appropriately concise, though it sacrifices necessary detail.

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?

This tool has 9 parameters and four distinct actions, yet the description provides only a one-line summary. It does not explain what each action does, what the output format is, or how parameters interact. Given the absence of output schema and annotations, the description is grossly insufficient for correct tool 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 0%, and the description only hints at the 'jsonPath' parameter via 'JSONPath filtering'. All other eight parameters (limit, offset, method, status, requestId, urlPattern, resourceType, action) are left undefined by the description, forcing the agent to infer meaning from parameter names and types alone.

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 clearly states the tool's function: monitoring and replaying network requests. It mentions a specific distinguishing feature (JSONPath filtering) and is easily differentiated from sibling tools, which focus on other browser interactions. The verb-resource combination is specific enough.

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 implies usage for network request inspection and replay, but it does not explicitly state when to use this tool over alternatives or how to choose among the 'list', 'details', 'replay', and 'clear' actions. Sibling tools do not offer network request functionality, so the context is inferable, but explicit guidance is missing.

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