adb_network_auto_connect

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

With no annotations, the description carries full burden. It explains the tool probes a single port (default 5555) and combines scan+connect. However, it does not disclose potential failures, timeouts, or whether it modifies device state (e.g., if already connected).

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 concise sentences: first states purpose, second gives usage guidance. No wasted words; every sentence adds essential information.

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 tool with no output schema and well-described parameters, the description is complete. It tells what the tool does, its limitation (single port), and when to use alternatives. No missing context.

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 covers all 3 parameters (100%). The description adds value by explaining the device parameter is used for 'ARP-based discovery' and clarifying the port default. This goes beyond the schema but does not fully compensate for missing output or nested structures.

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 tool discovers and auto-connects to ADB devices on the local network, combining scanning and connecting. It distinguishes itself from siblings by specifying when to use adb_network_scan and adb_connect instead.

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 provides when-to-use and when-not-to-use: 'if you need to cover the full ADB port range (5555-5558) use adb_network_scan first, then adb_connect.' This directly guides the agent to alternative tools.

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