playwright__browser_network_request

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds clarity about returning full vs. partial data and mentions saving to a file via the `filename` parameter, which is useful behavioral context beyond the annotations.

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 concise (two sentences) and front-loaded with the primary purpose. However, it could be slightly more structured, e.g., by separating the primary use from the optional `part` behavior more clearly.

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?

Given the input schema is comprehensive (100% coverage) and there is no output schema, the description adequately explains what the tool returns and how to use it. It references the sibling tool for context, which is helpful. It might be improved by mentioning expected data formats or caveats about large responses.

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 parameters well. However, the description adds no additional semantics beyond what the schema provides (e.g., it does not explain how the index relates to the list output, or how file saving works). This lack of extra context for a complex tool with file output drags the score down.

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 clearly states the tool returns full details (headers and body) of a single network request, and allows returning a single part via the `part` parameter. It also references the sibling tool `browser_network_requests` for the index number, distinguishing its purpose from the list tool.

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 implicitly guides use by stating to use the number from `browser_network_requests`, which establishes a prerequisite. However, it does not provide any when-not-to-use guidance or mention alternatives for related tasks like filtering or multiple requests.

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