browser_net_emulate_conditions

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

With no annotations, the description must disclose behavioral traits. It only says 'Emulate network conditions (throttling)' but does not explain the effect scope (all pages or current?), persistence, or side effects. The schema parameters hint at behavior (offline, latency, throughput) but the description adds no extra 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 extremely concise (8 words plus '(see browser_docs)'). While it avoids fluff, it is somewhat under-specified for a tool with four required parameters. It could benefit from a brief sentence on usage or effects.

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, no annotations, and the description is minimal. It fails to explain the tool's return value (e.g., whether it returns success or applies settings). Given the complexity of network throttling (4 parameters, all required), the description is incomplete.

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 100% description coverage for all four parameters (offline, latency, downloadThroughput, uploadThroughput). The description adds no additional meaning beyond the schema; the baseline is 3.

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 it emulates network conditions (throttling), which is a specific verb+resource. It distinguishes itself from sibling tools like browser_net_get_requests or browser_net_set_request_blocking by focusing on throttling. However, it could be slightly more precise about the scope.

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?

No usage guidance is provided. The description does not mention when to use this tool instead of other browser networking tools, nor does it give any context about prerequisites or alternatives.

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