Toggle Wifi

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates the operation. It does not disclose that disabling Wi-Fi disconnects connected clients, whether the change persists across reboots, or whether special permissions are needed.

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 single phrase is front-loaded and free of waste, but it is under-specified rather than genuinely concise. Brevity here reflects missing information, not efficient communication.

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?

An output schema exists, so return values need not be explained, but the tool is a state-changing network operation with two undocumented parameters and no annotations. The bare phrase leaves the agent without enough context to call it correctly, particularly regarding the 'radio' parameter.

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 description coverage is 0% for both parameters, and the description adds nothing: the 'radio' parameter with default '2g' has no enum or explanation anywhere, so an agent cannot know valid values or what it controls. 'enabled' is self-evident, but the ambiguous 'radio' parameter is left entirely 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?

The description names a clear verb pair (enable/disable) and resource (Wi-Fi), so an agent can tell this apart from settings siblings like get_wifi_basic_settings or set_wifi_ssid. However, it does not specify scope, such as whether it toggles all radios or one band, leaving the 'radio' parameter's role unexplained.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The description gives no indication of when toggling Wi-Fi is appropriate versus configuring it via set_wifi_ssid or get_wifi_basic_settings.

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