set_network_conditions

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

With no annotations provided, the description carries full burden. It states that the tool applies a preset, but does not disclose behavioral traits such as whether the change persists across navigations, if it resets other conditions, or any side effects (e.g., affecting all tabs).

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 short (two lines) with a clear list of options. However, the structure could be improved by front-loading the action and separating the reference to another tool more clearly.

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?

Given the tool has an output schema (not provided), the description need not explain return values. It is adequate for a simple one-parameter tool but lacks context on scope (e.g., per-tab or global) and does not mention error cases or confirmation of application.

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 the description must compensate. It lists the allowed profile values ('offline', 'slow-3g', etc.) and directs to 'list_network_profiles' for numeric details, adding meaning beyond the schema's plain string type.

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 verb ('Apply') and the resource ('named network-throttling preset'), and lists the specific preset options. It distinguishes from siblings like 'list_network_profiles' (which provides the numeric values) and 'set_cpu_throttle' (for CPU throttling).

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 implies usage by referencing 'list_network_profiles' for numeric values, but does not explicitly state when to use this tool versus alternatives like 'set_cpu_throttle' or other network-related tools. No exclusions or prerequisites are mentioned.

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