adb_bluetooth_firmware

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

No annotations provided, so description carries full burden. It discloses that MAC address and device name are opt-in only, which is good. However, it doesn't mention permissions required, read-only nature, or side effects. For a read tool, it's partially transparent but could be more detailed.

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, front-loaded with core info, zero waste. First sentence lists all reportable items, second clarifies identifier handling. Every word earns its place.

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?

For a read-only info tool with no output schema, description comprehensively lists returned data (firmware version, BT version, chipset, state, profiles, LE capabilities, bonded count). Also explains opt-in identifiers. No 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 coverage is 100%, so description adds minimal value. The schema already describes both parameters (device serial, boolean includeIdentifiers). Description repeats 'opt-in only' which is in schema. 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?

Description clearly states purpose: Bluetooth firmware and chipset identification. Lists specific data reported (firmware version, BT version, etc.), distinguishing it from sibling firmware tools like adb_gps_firmware, adb_nfc_firmware, adb_wifi_firmware. Verb 'reports' plus resource 'Bluetooth firmware' is 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?

No explicit when-to-use or when-not-to-use guidance. Implied usage for retrieving Bluetooth firmware details, but no mention of alternatives or exclusions. Lacks context like 'Use this to identify Bluetooth version and chipset; for detailed radio info, use adb_baseband_info'.

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