browser_get_network_logs

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

No annotations are provided, so the description must bear full responsibility for behavioral disclosure. It only says 'Get captured network request logs,' which implies a read operation, but it does not clarify whether retrieving logs clears them, whether logs are cumulative over multiple calls, or any other behavioral traits. For a tool with zero annotation coverage, this is insufficient transparency.

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 two sentences, front-loaded with the main purpose, and every sentence adds value. No extra 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?

Given the tool's simplicity, the presence of an output schema (covering return values), and the clear prerequisite, the description is fairly complete. It could mention that the parameters help filter the logs, but the schema already covers that, so this is a minor gap.

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 four parameters. The description adds no additional detail about the parameters beyond the prerequisite. According to guidelines, baseline is 3 with high coverage, which is appropriate.

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 'Get captured network request logs' using a specific verb and resource. It distinguishes itself from the sibling tool 'browser_enable_network_log' which enables logging. However, it could be slightly more explicit about the fact that it retrieves logs, so it's not a perfect 5.

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 states the prerequisite: 'Requires browser_enable_network_log to be called first.' This tells the agent when to use this tool (after enabling) and implies that if logging isn't enabled, the agent should call 'browser_enable_network_log' first. No additional exclusions are needed for this simple tool.

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