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

No annotations are provided, so the description carries the full burden. It discloses that requests are buffered from load, which is a meaningful behavioral trait (data availability depends on page open time). It also clarifies the scope is the DESKTOP grid browser page, not a device. It doesn't mention whether the buffer is cleared on refresh or how long it persists, but the key behavioral constraints are disclosed.

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?

Three sentences, each earning its place: what it does, how to filter, and what it is not. The critical scoping constraint (DESKTOP grid browser page, not a device) is front-loaded. No wasted words.

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 read-only network log tool with a complete schema, the description covers the essential context: scope, buffering behavior, and sibling alternatives. It doesn't describe the output format, but there is no output schema and the description mentions status codes, which gives a reasonable expectation. The main gap is not stating whether the buffer is per-page or per-session, but this is minor given the explicit 'since it opened' phrasing.

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 all three parameters. The description adds a usage hint for `filter` (narrow to an API path) and implies `pageId` comes from web_navigate, which is already in the schema. The description doesn't add much beyond the schema, but the schema is complete, so 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 states a specific verb and resource: network requests made by the DESKTOP grid browser page (by pageId) since it opened, with status codes. It also explicitly distinguishes itself from device-level network capture tools by saying 'NOT a device' and naming the alternatives. This clearly differentiates it from siblings like android_devtools_capture_network and ios_safari_capture_network.

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 explicitly says when to use this tool (for the DESKTOP grid browser page by pageId) and when not to use it ('NOT a device'), and names the alternatives for real phone or tablet (android_devtools_capture_network or ios_safari_capture_network by udid). It also gives a usage hint: 'Use `filter` to narrow to an API path.' This is explicit routing guidance.

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