adb_network_device_ip

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

No annotations are provided, so the description must cover behavioral traits. It only states the main action (get WiFi IP) and a use case. Missing details include prerequisites (e.g., device must be connected via USB and have WiFi enabled), error behaviors, or side effects. This is minimal disclosure for a tool that modifies network state.

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 two sentences long, with the first sentence stating the core purpose and the second providing context. No extraneous information, ideal length for a simple tool.

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 one parameter and no output schema, the description is adequate but not fully complete. It covers purpose and a use case but does not describe the output format, error states, or prerequisites. Considering the tool's simplicity, it could be better but meets minimum requirements.

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 has 100% coverage for the single parameter 'device' with a description 'Device serial'. The description does not add extra meaning beyond the schema, such as whether the parameter is optional or what happens if omitted. Baseline score of 3 is appropriate as the schema already documents the parameter.

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 'get's the WiFi IP address' using a specific verb and resource. It also provides a practical use case for switching to wireless debugging, making its purpose unambiguous. However, it does not explicitly differentiate from sibling tools like adb_tcpip or adb_network_auto_connect, which could be related.

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 a usage scenario ('useful for switching from USB to wireless debugging'), giving context on when to use it. However, it lacks explicit instructions on when not to use it or mentions of alternative tools, such as adb_tcpip for enabling wireless mode.

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