adb_nfc_firmware

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

No annotations are provided, so the description must carry the full burden. It implies a read-only operation (identification) but does not explicitly state that no device state is modified, or mention potential failure conditions (e.g., missing NFC hardware). The parameter hints about 'verbose vendor builds' add some context.

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 sentence that efficiently conveys the tool's purpose and output items. It could be slightly more structured, but it remains clear without redundancy.

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 absence of output schema and annotations, the description covers key aspects of what the tool returns. However, it omits potential context like required NFC state or error scenarios. The included list of output items is fairly comprehensive.

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%, with both parameters ('device' and 'maxLines') documented. The description adds no additional parameter meaning; it focuses on the output. 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 clearly states 'NFC controller firmware identification' and enumerates specific output details (controller type, versions, technologies, secure element, HCE). This differentiates it from sibling tools like adb_gps_firmware, adb_wifi_firmware, and adb_firmware_probe.

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 does not provide any guidance on when to use this tool, prerequisites, or when alternatives might be better. It only describes the output, leaving the agent to infer proper usage context.

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