adb_bluetooth_firmware

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

With no annotations, the description carries full burden. It discloses that MAC/name are opt-in (permanent identifiers) and lists reported data. However, it does not mention if Bluetooth must be enabled or any error conditions, which are relevant for a hardware identification tool.

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 sentences, no fluff. First sentence states purpose, second lists output fields and identifier note. Efficiently structured and scannable.

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 no output schema, the description covers the main return types (firmware version, BT version, chipset, etc.) and identifier policy. Missing details like output format or error handling, but still provides solid context for an agent.

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 coverage is 100%, baseline is 3. The description adds value for includeIdentifiers (emphasizing opt-in for permanent identifiers) and maxLines (advising to raise for verbose vendor builds), enhancing understanding beyond schema descriptions.

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 Bluetooth firmware and chipset, listing specific data reported (firmware version, BT version, chipset model, etc.). It distinguishes from other firmware tools by specifying Bluetooth-specific information, and clarifies that MAC/device name are opt-in.

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 Bluetooth firmware info but does not explicitly differentiate from sibling tools like adb_firmware_probe or adb_wifi_firmware. It provides no guidance on when to use this over alternatives.

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