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

With no annotations, the description carries the behavioral burden. 'Get' implies a read-only operation and the description discloses what data will be retrieved. However, it does not address failure modes, prerequisites such as an active WiFi connection, or whether the device must be reachable.

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 sentence that is front-loaded with the action and resource, followed by the key output fields. There is no redundant information or filler.

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 low-complexity, one-parameter read tool with no output schema, the description is mostly sufficient: it names the source, the required identifier context, and the expected return contents. It could be more complete by noting error conditions or assumptions about device connectivity, but these are minor gaps.

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?

The schema already documents udid as 'Device serial number (UDID)' with 100% coverage, so the baseline applies. The description adds no further parameter-level detail beyond tying the tool to Android devices.

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 states a clear verb ('Get') and resource ('network info from an Android device') and enumerates the returned fields (WiFi SSID, IP address, signal strength). It is unambiguous, though it does not explicitly contrast itself with sibling network-related tools such as android_devtools_capture_network or android_traffic_flows.

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 on when to use this tool versus alternatives, no prerequisites, and no mention of when it should not be used. The description implies a straightforward read operation but leaves selection criteria entirely to inference.

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