adb_gps_firmware

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

The description details what the tool reports (constellations, signal types, raw measurements, A-GPS modes, etc.), implying a read-only, non-destructive operation. Without annotations, it carries the burden and does well, but could explicitly state it is read-only.

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 a single paragraph that packs substantial information without being verbose. It is well-structured and front-loaded with the core purpose.

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?

Given the complexity of possible outputs (constellations, signals, dual-frequency, A-GPS, etc.) and no output schema, the description comprehensively covers all major aspects, making it sufficient for agent understanding.

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 schema with 100% coverage. The description adds no additional meaning beyond the schema, which is adequate for a single, straightforward 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 it identifies GNSS/GPS chipset and firmware, listing specific hardware details and supported constellations. It distinguishes itself from general firmware probes (e.g., adb_firmware_probe) by being GPS-specific.

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 use for GPS firmware identification and mentions relevance to IMSI catcher research, but does not explicitly state when to use this tool versus alternatives like adb_firmware_probe or other firmware tools in the sibling list.

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