connect_device

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

No annotations are present, so the description carries the full behavioral burden. It states the connection mechanism but does not disclose side effects, success/failure behavior, prerequisites such as the device already listening on the port, or whether the connection persists.

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 compact sentence with no filler, and the Android and wireless-debugging qualifiers add useful context. It is appropriately concise, though it has no structured detail beyond the core statement.

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?

Given the low parameter complexity and complete schema coverage, an agent can likely invoke the tool correctly. However, the description omits when the connection should be established, what a successful connection looks like, and what errors might occur, which are meaningful gaps for a stateful connection action.

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 100%, so the schema already documents both parameters and the default port. The description adds only the TCP/IP/wireless debugging context, which is helpful but does not materially extend the parameter definitions.

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 names a specific action ('Connect'), a resource ('a device over TCP/IP (wireless debugging)'), and scopes the tool to Android. It is clear and not tautological, though it does not explicitly contrast with siblings such as list_devices or device_info.

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 connect_device versus alternatives, when not to use it, or what setup is required first. The wireless-debugging context implies a use case, but the description never states it.

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