adb_cell_identity

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

No annotations are provided. The description only states it parses dumpsys data but does not disclose behavioral traits like required permissions, side effects, or whether it is read-only. With no annotations, this is insufficient.

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, concise and front-loaded with key information. No redundant phrases.

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?

The description lists extracted fields but omits important context such as Android version requirements, output format, or whether it works on emulators. Given the simplicity of the tool (single required param, no output schema), it is minimally adequate.

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% (the only parameter 'device' has a description). The tool description does not add any additional meaning beyond what the schema provides. 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 'extracts detailed cell identity information' with specific fields (CID, TAC/LAC, EARFCN/ARFCN, PCI, PLMN, network type). It also mentions parsing from dumpsys, which distinguishes it from siblings like adb_neighboring_cells that focus on neighbor cells.

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 'cellular network analysis' but provides no guidance on when to use this tool versus alternatives (e.g., adb_signal_detail, adb_neighboring_cells). No when-not-to-use or prerequisite information is given.

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