connect_android_over_wifi

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

No annotations exist, so the description carries the full burden. It does disclose a real behavioral constraint — the target must be an mDNS-advertised TLS ADB service — but says nothing about whether connection requires prior pairing/authorization, whether the device becomes persistently registered, whether it is idempotent, or how failures (stale advertisement, TLS handshake rejection) surface.

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?

A single front-loaded sentence with no filler; the key qualifier (must be currently advertised) is placed where it will be read first. It is arguably too terse for a tool with an ambiguous required argument, but nothing in it is wasted.

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?

An output schema exists, so return values need no explanation, but for a connection tool with zero annotation coverage and one undocumented required parameter the description leaves critical gaps: endpoint format, pairing prerequisite, and side effects on device state. An agent could not confidently invoke it without guessing.

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 0% and the only parameter, `endpoint`, is a bare string with no format hint. The description hints the value comes from an mDNS advertisement but never says whether it is a service instance name, host:port, or a serial — a caller cannot reliably construct it from this text.

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?

States a specific verb (Connect) and a specific resource (an Android TLS ADB service), plus a qualifying scope: only services currently advertised via ADB mDNS. This is materially clearer than the bare tool name and separates it from generic discovery tools, though it never names the sibling it must be sequenced around (pair_android_over_wifi).

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?

"Currently advertised by ADB mDNS" implies the precondition that discovery must have happened and that the service must still be live, which is useful implicit guidance. But there is no explicit when-to-use, no statement of whether pairing is a required predecessor, and no exclusion relative to pair_android_over_wifi or discover_wireless_devices.

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