Show network request details

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

Annotations already declare readOnlyHint and destructiveHint as false, so the behavioral safety profile is covered. The description adds the ability to retrieve partial data via the 'part' parameter, which is useful context beyond annotations but does not disclose error behavior or format of the response.

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 sentences: the first states the core function, the second provides a critical usage hint. Every sentence serves a purpose with no wasted words. Front-loaded with the primary behavior.

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?

No output schema exists, so the description must convey what is returned. It mentions 'headers and body' but does not specify the structure or provide details on error cases (e.g., invalid index). Adequate for a simple tool but leaves the output format ambiguous.

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 coverage is high (75% per context), so baseline is 3. The description adds context for the 'index' parameter by linking it to browser_network_requests, which is not in the schema. Other parameters like 'part' and 'filename' are already well-described in the schema, so minimal additional value.

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 it returns full details (headers and body) of a single network request, or a part if 'part' is set. Distinguishes from sibling 'browser_network_requests' by specifying it operates on a single request selected by index.

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?

Explicitly instructs to use the index from browser_network_requests, establishing a clear usage sequence. Does not explicitly mention when not to use it or alternatives, but the dependency is clear and sufficient for most agents.

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