browser_network_request

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

Discloses auto-capture for XHR/fetch and potential delayed body population for recent requests. With no annotations, this adds valuable behavioral context, though could mention whether it requires an active session or if it's read-only.

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 concise sentences, front-loaded with the key action and then details. Every sentence adds value with no redundancy.

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?

Covers main functionality and important behavioral notes. Could be more complete by referencing the sibling tool for listing requests or explaining session_id. Output schema exists, so return value details not required.

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?

Describes index and url_contains parameters' purpose clearly, but does not explain session_id. Schema coverage is 0%, so description partially compensates but misses one parameter. No details on the format of url substring.

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?

Clearly states 'Get one request's full detail' with specific resource. Differentiates from sibling 'browser_network_requests' by focusing on detail retrieval, but does not explicitly mention the sibling or when to use each.

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?

Provides two matching methods (list index or url substring) but no guidance on when to prefer one over the other, nor when not to use this tool. No mention of prerequisites like session existence.

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