get_network_logs

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'recent network request logs' without specifying what 'recent' means, whether logs are cleared after retrieval, or what format the logs take. This is insufficient for an AI agent to understand side effects or limitations.

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 a single, front-loaded sentence with no wasted words. It efficiently communicates the core purpose.

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 tool's simplicity (1 parameter, no nested objects, has output schema), the description should still clarify what CDP is and what 'network request logs' entail. Without this, an AI agent may not understand the tool's role within the broader set of sibling tools (e.g., browser automation and network manipulation).

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 input schema has one parameter (limit, default 20) with 0% description coverage. The description does not explain the purpose or effect of this parameter, leaving the agent without crucial context for proper invocation.

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's purpose: 'Get recent network request logs captured via CDP.' It uses a specific verb ('Get') and resource ('network request logs'), and implicitly distinguishes from sibling tools like get_console_logs or network manipulation tools.

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 implies usage after CDP captures network data but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools such as wait_for_network or list_interceptions.

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