get_network_logs

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

No annotations are provided, so the description bears the full burden. It mentions 'capture' but does not clarify if this is a one-time operation, if it waits for network events, or if it modifies browser state. It fails to disclose important behavioral traits such as whether logs are cleared or how long the capture lasts.

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 at two sentences, with the purpose front-loaded. It is well-structured and each sentence adds value, avoiding unnecessary fluff.

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?

Despite 8 parameters and no output schema or annotations, the description omits details on many parameters and behavioral aspects. It does not explain the return format, pagination, or limits, nor does it clarify the role of parameters like waitTime or includeBody. The description is incomplete for a tool of this complexity.

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?

The description adds meaning to some parameters by mentioning filtering by URL pattern, HTTP method, status code, and resource type, which map to properties in the filter object. However, other parameters like browser, maxLogs, waitTime, includeBody, maxBodySize, and includeHeaders are not described. Given the 0% schema coverage, the description partially compensates but is insufficient for all parameters.

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 that the tool captures network requests and responses for debugging and API verification, which is a specific and well-defined purpose. It also mentions filtering capabilities, which adds clarity. However, it does not explicitly differentiate from sibling tools like get_console_logs, though the purpose is distinct enough.

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 says it is 'essential for understanding API calls and debugging network issues,' which implies when to use it. However, it does not provide explicit guidance on when not to use it or mention alternatives, such as using console logs for JavaScript errors.

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