browser_network_state_set

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states the cause-and-effect behavior: setting offline=true simulates offline, and offline=false restores connectivity. It does not detail persistence across pages or the impact on in-flight requests, but the core mutation is transparent.

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 entire description is one compact sentence with no filler. The behavioral meaning is front-loaded, and both parameter mappings are stated efficiently.

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?

For a simple one-boolean setter with no output schema, the description gives enough information to invoke the tool correctly. It stops short of explaining scope or side effects in detail, but nothing essential is missing for basic usage.

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 0%, but the description fully compensates by explaining the single boolean parameter: true means simulate offline and false means restore connectivity. This gives the agent complete semantic understanding that the bare schema lacks.

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 uses a specific verb ('Set') with a clear resource ('network state') and explicitly defines the two possible states: offline simulation and restored connectivity. This makes it easy to distinguish from read-only siblings like browser_network_requests or browser_status, even without opening the schema.

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?

There is no guidance about when to use this tool versus alternatives that also affect network behavior, such as browser_route_block or browser_route_mock. The description only explains the parameter; it does not mention prerequisites, exclusions, or scenarios like testing offline behavior.

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