browser.get_network_log

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

No annotations provided, description includes PII-scrubbing disclosure. However, lacks explicit mention of read-only nature, whether log is cleared, or performance impact. Adequate but not comprehensive.

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, no wasted words. First sentence states core function, second adds key details (filters, PII scrubbing). Efficient and well-structured.

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, description implies entries but lacks details on structure (status codes, headers, bodies). No mention of pagination or limit behavior. Adequate but with notable gaps.

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 0%, description adds meaning to method and url_contains parameters by mentioning filtering. Does not describe session_id or limit parameters, so coverage is incomplete. Baseline 3 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?

Description clearly states verb 'return' and resource 'captured HTTP request/response entries' for a session. It distinguishes from sibling tools like get_console or get_page_errors by focusing on network traffic.

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?

Implies usage for inspecting network traffic but provides no explicit guidance on when to use vs alternatives like get_request_failures or get_console. No 'when not to use' statements.

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