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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuine context beyond that: data is captured automatically rather than on demand, only the most recent requests are returned, and response/request bodies are deliberately not available.

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 dense paragraph, front-loaded with purpose and return fields, then usage, then constraints. Every clause carries information (fields returned, automatic capture, use case, session family, body limitation, platform scope); nothing is padding.

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?

There is no output schema, so the description compensates by listing exactly what the response contains and what it omits (bodies). Combined with the sessionId-family note and the browser-only constraint, an agent has everything needed to call it and interpret results.

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 type, limit, sessionId and failuresOnly are already documented in the schema itself. The description only reinforces sessionId reuse across the family and hints at the failuresOnly use case; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (read network requests for a browser session), enumerates the returned fields (method, URL, status, type, timing, size), and scopes it to browser sessions, which separates it from the device/android/ios devtools capture siblings. An agent can identify the tool without opening the schema.

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?

Gives explicit when-to-use ('find failing (4xx/5xx) or slow requests') and states the precondition that it takes the same sessionId as the rest of the family, plus the exclusions that bodies are unavailable and it is browser-only. It stops short of naming a specific alternative sibling for the non-browser case, so not a full 5.

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