Request details

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior, namely that large or binary bodies are diverted to a file rather than returned inline, and that WebSocket frames and initiator stacks are included in the payload. It omits failure behavior for unknown/expired request ids and any caveats about payload size, so it stops short of a 5.

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?

A single front-loaded sentence that enumerates return contents with one clarifying parenthetical; every clause carries information and nothing is redundant with the annotations.

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?

With no output schema, the description effectively serves as one by listing every returned section, which is exactly what an agent needs before calling. Missing are the error case (stale/unknown request id) and explicit linkage to network_requests for obtaining the id, minor but real gaps.

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 coverage is 100% so the baseline is 3, but the description adds real meaning by explaining that the response body may be returned as text or written to a file when binary/large, which clarifies the interplay of the body, savePath, and maxBodyChars parameters. It does not explain id format or tabId scoping, which the schema carries on its own.

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 names a specific resource ('one request') and enumerates exactly what is retrieved (headers, bodies, timings, security, initiator stack, WebSocket frames), which makes it clearly distinct from the list-style sibling network_requests. It never states the verb (fetch/retrieve) or explicitly routes the agent from network_requests, so it falls short of a 5.

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 gives no when-to-use, when-not-to-use, or alternative guidance; it never says to call network_requests first to get an id, or when to prefer network_har for bulk data. Usage must be inferred entirely from the name and schema.

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