clear_network_requests

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

Despite destructiveHint=true annotation, description adds detail on what is irreversibly cleared (request queue, cached response bodies, initiator maps) and what is unchanged (cookies, HTTP cache, storage), exceeding annotation info.

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?

Concise paragraph with front-loaded action, followed by usage guidance, behavioral specifics, and contrast with sibling; every sentence adds value with no redundancy.

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 simple single-parameter tool with output schema, description fully covers purpose, usage, behavioral boundaries, and parameter semantics without missing critical context.

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 100% for the single parameter 'confirm', and description reinforces its meaning as required for irreversible capture cleanup, adding nuance beyond schema.

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 uses specific verb 'discard' and resource 'captured HTTP(S) evidence', clearly distinguishing from sibling clear_site_data by stating what it does not affect.

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 when to use ('immediately before reproducing an action when a clean network capture window is needed') and when not to use ('do not use it to reset login, cookies, cache'), with reference to alternative clear_site_data.

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