Network log

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

The annotations declare only readOnlyHint=false, which the description never explains; notably the schema's 'clear' action is the mutating operation and the description never mentions that the log can be cleared or that doing so is destructive. It does add genuinely useful context beyond annotations — URLs are redacted per BROWSER_MCP_REDACT_PARAMS — so it is not a 2.

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?

Two tight sentences, front-loaded with the core capability and followed by the redaction caveat, which is genuinely load-bearing. Nothing is padded, though the redaction sentence could have been paired with a note on the clear action instead of standing alone.

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 six parameters, no output schema, and low schema coverage, the description should carry more weight than it does. It conveys what is captured but omits the clearing behavior, limit/default semantics, and any indication of result shape or volume, leaving real gaps for a tool with a mutating action.

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 only 33% (only 'type' and 'filter' are documented), so the description needs to compensate. It partially does: 'status', 'type' and 'failures' map onto status_min, type and failed_only, and the redaction note informs URL filtering, but 'limit' and 'action' remain unexplained in both places.

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 gives a specific verb ('Inspect') and resource ('requests made by pages in this browser session') and enumerates the fields surfaced (status, type, size, duration, failures). It is clear on its own, but it never distinguishes itself from plausible siblings such as 'perf' or 'console', so it stops 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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'in this browser session' implies scope, but an agent must infer on its own whether to reach for this tool versus 'perf' or 'console'.

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