adb_airplane_cycle

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

Description explains the behavioral effect (forces cellular re-registration). With no annotations, it carries the full burden. Could mention any prerequisites or side effects, but the core behavior is clear.

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?

Extremely concise: two sentences. First sentence states the action, second provides context and purpose. No unnecessary words.

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 simple toggle tool with no output schema, the description is fairly complete. It explains the delay and the purpose. Could mention what happens on failure, but not essential given the tool's simplicity.

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?

Input schema has 100% description coverage for both parameters (delaySeconds with default, device with serial). The description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Clearly states the action ('Cycle airplane mode on then off after a delay') and the purpose ('Forces cellular re-registration — useful for radio diagnostics and network testing'). Distinct from sibling tools like adb_airplane_mode which likely sets mode statically.

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?

Explicitly specifies use cases (radio diagnostics, network testing). Does not provide explicit when-not-to-use or alternatives, but the context implies it's for temporary cycling rather than setting a fixed mode.

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