airplane_mode_toggle

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal the primary state change (turning airplane mode on/off), but it says nothing about side effects, permissions, device prerequisites, or impact on network connectivity.

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 a single concise sentence with no redundant wording. It is easily parseable and front-loads the core purpose, though it is quite terse and could carry more supporting detail without becoming bloated.

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 tool with only two parameters and an output schema, the description is minimal but not fully complete. It omits when to use the tool, how the optional serial parameter affects behavior, and any side effects of toggling airplane mode, which an agent would need for reliable 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 description coverage is 0%, so the description must compensate for missing parameter explanations. It indirectly maps 'enabled' to turning airplane mode on/off, but it does not clarify the role of the optional 'serial' parameter or explain how the required boolean should be interpreted.

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 identifies the resource (airplane mode) and the specific action (switching it on or off), which is more informative than the tool name alone. This also separates it from sibling tools like wifi_toggle or bluetooth_toggle because it targets airplane mode specifically.

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 guidance about when to use this tool versus alternatives such as wifi_toggle or set_mode. The description simply states what the tool does without providing context, exclusions, prerequisites, or example scenarios.

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