adb_neighboring_cells

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

With no annotations, the description clearly explains the tool's output (neighboring cells, identities, signal strengths) and implies a read‑only operation. It lacks details on permissions or device requirements but is sufficient for typical ADB use.

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?

Two concise sentences: the first specifies the tool's action and output, the second its utility. No unnecessary words, front‑loaded, and every sentence adds value.

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 tool with one optional parameter and no output schema, the description covers core functionality and use cases. It could elaborate on output format or prerequisites but is reasonably complete.

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 only parameter `device` is fully described in the input schema ('Device serial'). The description adds no further context, so with 100% schema coverage, a baseline of 3 is appropriate.

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 lists all visible neighboring cells (LTE/5G/WCDMA/GSM) with identities and signal strengths, using a specific verb and resource, and distinguishes from serving cell or other network tools.

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 mentions use cases (surveys, coverage analysis, characterization) but does not explicitly compare to alternatives like adb_cell_identity or adb_signal_detail, nor states when not to use.

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