emulate_network

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

No annotations exist, so description carries full burden. It mentions throttling and CDP source but does not disclose potential side effects like disrupting ongoing requests or persistence of settings. 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?

Three sentences: purpose, preset enumeration, and override/reset instructions. Front-loaded, no redundant information, every sentence earns its place.

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?

With an output schema present, return values need not be described. Tool has 4 parameters, all covered. Lacks mention of whether settings persist across navigations, but overall sufficient for agent invocation.

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%, so description must compensate. It explains preset values and introduces override knobs (latency_ms, download_bps, upload_bps), adding meaning beyond schema titles. All parameters are addressed.

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 throttles network via CDP Network.emulateNetworkConditions, and lists presets matching Chrome DevTools. The name aligns well with the verb 'emulate' and resource 'network', distinct from siblings like emulate_cpu or emulate_device.

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?

It explicitly lists presets (offline/slow-3g/3g/slow-4g/4g/wifi/no-throttle) and explains how to reset with 'no-throttle' or override with individual parameters. It does not explicitly state when not to use or contrast with other network-related tools, but the context is clear.

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