set_network_status

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Simulates network connectivity changes' gives a minimal hint that this is a simulation/emulation rather than a real change, which is useful, but it doesn't disclose scope, side effects, whether it affects only the app or the whole device, or whether changes persist.

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 short sentence. There's no filler or redundancy. While it's brief, it's technically efficient—however, the brevity comes at the cost of substance, so it earns a 4 rather than a 5.

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 mutation tool with no annotations and no output schema, the description is under-specified. It doesn't clarify the relationship to sibling tool intercept_network, doesn't explain the scope of the simulated change, and doesn't indicate what the result/effect of setting wifi=false would be. A 1-parameter tool is simple, but the ambiguous relationship to siblings and lack of behavioral detail leaves gaps.

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 100% with a single boolean 'wifi' parameter directly described as 'Enable or disable WiFi'. The description adds the context that this is network connectivity simulation, which slightly supplements the schema. Baseline 3 is appropriate since the schema already fully documents the parameter.

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 'Simulates network connectivity changes' uses a verb and resource but is very vague. It doesn't specify that this toggles WiFi connectivity, nor does it distinguish itself from sibling tools like intercept_network (which likely modifies network interception). The purpose is only loosely conveyed.

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 guidance is given about when to use this tool versus intercept_network or other network-related siblings. There's no mention of scenarios (test conditions, offline reconnection checks) or exclusions. The agent has no way to know if this is testing-related or how it differs from intercept_network.

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