connect_device

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the connection action but does not mention side effects, whether it replaces an existing connection, authentication requirements, or the need for the device to be in ADB-over-Wi-Fi mode. This leaves behavioral ambiguity.

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 sentence that is direct, front-loaded, and contains zero redundant words. It efficiently conveys the core action and key parameters.

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 only two parameters and no output schema, the description covers the essential purpose and connection method. However, it omits potential prerequisites like the device being previously configured for TCP/IP, which would make the invocation more robust. Still, it is a straightforward tool and the description is largely sufficient.

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% with both host and port having descriptions. The description echoes 'IP address and optional port' but adds no new semantic detail beyond the schema, so it meets the baseline for well-documented parameters.

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 uses a specific verb 'connect' and names the resource 'Android device' over TCP/IP (Wi-Fi), which clearly distinguishes it from siblings like disconnect_device and list_devices. It states the exact action and method.

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 implies usage for establishing a Wi-Fi connection to an Android device before other operations, but it does not explicitly mention when to use this tool versus alternatives like USB connection or when not to use it. It lacks exclusions or prerequisite context.

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