adb_airplane_cycle

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

With no annotations, the description carries full burden. It describes the cycle process and its intent but does not mention potential side effects like temporary network disconnection, permission requirements, or whether the tool is read-only or destructive. The description is adequate but not exhaustive.

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?

Two sentences, no filler. Every word serves a purpose: action, effect, and use case. Highly compact and efficient.

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?

The tool is simple with two fully described parameters. No output schema is provided, and the description omits return values or result format. Some behavioral details (side effects, permissions) are missing. Adequate for a straightforward diagnostic tool but not fully comprehensive.

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%, so baseline is 3. The description adds 'forces cellular re-registration' context but does not elaborate on parameter usage beyond what the schema provides. The phrase 'after a delay' aligns with the delaySeconds parameter, adding marginal value.

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 action ('Cycle airplane mode on then off after a delay') and its purpose ('Forces cellular re-registration — useful for radio diagnostics and network testing'). This distinguishes it from sibling 'adb_airplane_mode' which likely sets mode rather than cycling.

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 provides clear use context ('radio diagnostics and network testing'), implying when to use. It does not explicitly state when not to use or mention alternatives, but the sibling list provides 'adb_airplane_mode' as a direct alternative. Lack of explicit exclusions prevents a 5.

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