adb_gps_firmware

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

No annotations exist, so the description carries the full burden. It discloses many behavioral aspects: what is reported (hardware, constellations, signals, raw measurements, A-GPS modes, etc.), including advanced capabilities like spoofing detection support. It lacks explicit statements about side effects or permissions, but the read-only nature is implied.

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 dense paragraph that packs all necessary information without excess words. Every sentence adds value, covering all key aspects of the tool's output.

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 tool's complexity and lack of output schema, the description thoroughly covers all reported data: hardware, constellations, signal types, dual-frequency, raw measurements, A-GPS modes, carrier phase, navigation message, and SUPL. No obvious 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?

Schema provides full parameter coverage with a description for 'device' ('Device serial'). The tool description does not add extra meaning beyond that. Baseline 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 explicitly states 'GNSS/GPS chipset and firmware identification' and enumerates specific aspects (hardware model, constellations, signal types, dual-frequency, raw measurements, etc.), clearly indicating what the tool does. It distinguishes itself from sibling tools by its specialized focus on GPS/GNSS firmware.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While the description implies usage for GPS/GNSS hardware and firmware analysis, it does not mention when not to use it or suggest alternative tools for other scenarios.

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