read_network_requests

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

With no annotations, the description carries the behavioral burden. It discloses that requests are automatically cleared on page navigation to a different domain and that cross-origin requests are included, which are non-obvious behaviors. This adds valuable context beyond the schema.

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 about four sentences and front-loads the purpose. There is slight redundancy between 'Read HTTP network requests' and 'Returns all network requests made by the current page,' but overall it is concise and each sentence contributes meaningful information.

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 description provides sufficient context for an agent to select and invoke the tool: what it does, when to use it, the automatic clearing behavior, and how to obtain a valid tab ID. With an output schema present, return values need not be detailed. It lacks only explicit alternative comparisons, but that is not critical here.

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 covers all 4 parameters with descriptions, so the description does not need to add parameter semantics. It only ties tabId to the tabs_context prerequisite, but this is already implied in the schema. Baseline 3 is appropriate.

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 reads HTTP network requests (XHR, Fetch, documents, images) from a specific tab, which distinguishes it from sibling tools like read_console_messages or get_page_text. It also specifies scope (cross-origin included), making the purpose unambiguous.

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 clear use cases (debugging API calls, monitoring network activity) and a prerequisite (use tabs_context if no valid tab ID). However, it does not explicitly mention when not to use the tool or directly compare with alternatives, so it lacks exclusions.

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