adb_firmware_diff

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

No annotations are provided, so the description must fully describe behavior. It fails to mention output format, side effects, prerequisites (device connection for 'current'), error handling, or underlying mechanism. This is a significant gap for a diff 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?

The description is two sentences, front-loading the main purpose and listing what is compared. No unnecessary words or redundancies; every sentence adds value.

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?

The description covers the 'what' but lacks detail on the output, error conditions, and prerequisite knowledge (e.g., what fingerprints are). Without an output schema, more context is needed for complete usage understanding, but it is minimally adequate.

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% with clear parameter descriptions in the schema. The tool description does not add additional meaning about parameters, so it meets the baseline of 3 for a fully covered schema.

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 the tool compares firmware components between two OTA fingerprints or current state, and lists specific components (baseband, bootloader, etc.). This distinguishes it from siblings like adb_firmware_history (history) and adb_firmware_probe (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 explains two primary use cases (fingerprint-to-fingerprint and current-to-fingerprint), giving clear context for usage. However, it lacks explicit guidance on when not to use it or alternatives, preventing a 5.

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