emulate_network_conditions

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

Without annotations, the description bears full responsibility for disclosing behavioral traits. It mentions simulation and reset but omits important details such as whether the conditions persist across tabs, affect other tabs, require any permissions, or have side effects like clearing cache or cookies. The description fails to convey the scope and lifetime of the simulated conditions.

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 three sentences long, front-loads the core purpose, and provides a key usage tip. Every sentence earns its place without redundancy or unnecessary detail.

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?

The tool has 7 parameters, including optional tabId and apiKey, but the description does not explain how they affect behavior, default scoping, or what to expect when combining parameters. With no output schema and no annotations, the description should cover more details about the tool's behavior and limitations to be complete.

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% coverage with decent descriptions for each parameter. The description adds value by specifically highlighting the reset parameter to restore normal conditions, which is not obvious from the schema alone. This enhances the agent's understanding of how to use the tool effectively.

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 the tool simulates slow or offline network conditions for testing page behavior on poor connections. This distinguishes it from sibling tools like emulate_device (which focuses on device emulation) and network logging tools, but it does not explicitly differentiate from other network-related tools such as intercept_requests.

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?

The description advises using the tool to test poor connections and mentions the reset parameter to restore normal conditions. However, it provides no guidance on when not to use it (e.g., for persistent network simulation across tests) or alternatives (e.g., intercept_requests for custom network manipulation).

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