reset_network_conditions

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

With no annotations, the description carries the full burden. It doesn't say what 'default' resolves to, whether it requires an active emulation session, whether it errors when no conditions are set, or whether the change is scoped to the session only.

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?

A single tight sentence with the action front-loaded. It is efficient, though its brevity borders on under-specification rather than optimal conciseness.

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 session-scoped mutation with no annotations, no output schema, and an undocumented required parameter, the description leaves key facts unstated: what default state is restored, and what happens if no emulation is active.

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% — sessionId has a format and pattern but no description of what a session is or how to obtain one. The description adds nothing about parameters, leaving the single required param semantically undocumented.

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?

States a specific verb ('Reset') and resource ('network conditions') with a clear end state ('to default'). It implicitly distinguishes itself from the sibling emulate_network_conditions, but never names that counterpart to make the pairing explicit.

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 when-to-use guidance is given. The natural trigger — undoing a prior emulate_network_conditions call on the same session — is left entirely to inference, and no prerequisites or conditions are stated.

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