list_network_requests

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the temporal scope ('since the last navigation'), which is real context beyond the annotations, but it omits return-volume behavior and the existence of preserved-request handling, leaving notable gaps for a list tool.

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?

A single front-loaded sentence with no filler. The scope constraint is stated immediately and nothing is wasted.

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 five-parameter read-only list tool with a fully documented schema but no output schema, the description covers the essential scope. The minor tension between 'most recent requests' and the schema's 'returns all requests when pageSize is omitted' is left unresolved, and no return shape is hinted at, but nothing critical is missing.

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 all five parameters (pageId, pageIdx, pageSize, resourceTypes, includePreservedRequests) are already fully documented in the schema. The description adds no extra parameter meaning, which is the expected baseline when the schema carries the load.

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?

States a specific verb (Lists) and resource (network requests) scoped to the target page, and the singular sibling get_network_request is implicitly contrasted by the plural naming. It stops short of explicitly differentiating itself from that sibling, so it lands just below the top tier.

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 phrase 'since the last navigation' implies a temporal scope but no explicit when-to-use, when-not-to-use, or alternative (e.g., get_network_request, list_console_messages) is named. The agent must infer when this tool is preferred over its sibling.

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