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

With no annotations provided, the description carries the behavioral disclosure burden. It covers read-only semantics, automatic capture, recent-request scoping, unavailable request/response bodies, and the browser-only limitation. It does not mention auth, rate limits, or side effects, but for a read tool the disclosed constraints are substantial.

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 front-loaded with the primary action and output fields, then adds only high-value behavioral caveats (automatic capture, most-recent behavior, no bodies, browser-only). Every sentence earns its place and there is no filler or restatement of the schema.

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 four-parameter tool with no output schema and no annotations, the description compensates well by listing returned fields, the failure-slow-use case, the family sessionId convention, and the absence of bodies. It omits some details like pagination beyond limit, but an agent has enough to invoke it correctly.

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 input schema already documents all four parameters individually. The description adds minimal semantic value beyond reinforcing 'most recent' for limit and 'same sessionId' for the session family, which the schema also states.

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 opens with a specific verb and resource: 'Read the NETWORK requests for a browser session,' and enumerates the exact fields returned (method, URL, status, type, timing, size). It conveys scope explicitly with 'Browser sessions only' and ties the sessionId to the session_* family, distinguishing it from broader network capture tools.

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 states when to use the tool: 'Use to find failing (4xx/5xx) or slow requests.' It implies the correct context by noting browser-session scope and automatic capture, but it does not name alternative sibling tools or state when not to use it.

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