browser_network_requests

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so safety is covered without repetition. The description adds valuable behavioral context: the results are numbered, scoped to page load, and intended to be consumed by browser_network_request. Missing pagination or snapshot semantics is a minor gap given the tool's simplicity.

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?

Two sentences with no filler. The first sentence front-loads the core action and temporal scope; the second sentence gives the essential follow-up instruction. Every word 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?

For a list/detail tool with no output schema, the description sufficiently explains return shape (numbered list), scope (since page load), and the next step (pass a number to browser_network_request). The schema covers parameter details. It is complete enough, though exact text/format of the list is left implicit.

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 100%, so the schema already documents filter, static, and filename. The description adds little direct parameter meaning, though the numbered-list phrasing explains how results connect to the sibling detail tool. Per baseline, this is adequate but not exceptional.

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 states a specific verb and resource: 'Returns a numbered list of network requests since loading the page.' It also clearly differentiates itself from the sibling browser_network_request by pointing to it as the detail-fetching counterpart. An agent can immediately tell the list operation from the detail operation.

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 routes the agent to browser_network_request when full details are needed, which is the key alternative for this list/detail pair. It does not enumerate when-not-to-use conditions against unrelated browser tools, but the usage context is clear enough for correct selection.

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