adb_snapshot_compare

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

With no annotations, the description must disclose behavioral traits. It implies a read-only operation, showing differences without side effects, but does not detail potential impacts (e.g., network usage, device load) or confirm non-destructive behavior.

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, efficient sentence that front-loads the action and then lists the outputs. It is concise, but could be slightly more structured (e.g., separate purpose from result).

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 simple inputs and lack of output schema, the description sufficiently covers the tool's function. It explains what it compares and what differences it shows, though it omits details like snapshot format or device requirement optionality.

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%; both parameters are described. The description adds context that snapshotPath is the snapshot to compare and device is the target, but this does not significantly enhance the schema's explicit 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 the tool's purpose: compare current device state against a saved snapshot. It specifies the outputs (added/removed packages, changed settings, property differences), making it distinct from siblings like adb_snapshot_capture or adb_firmware_diff.

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 provides no guidance on when to use this tool versus alternatives (e.g., adb_multi_compare, adb_firmware_diff). It does not mention prerequisites, such as requiring a previously saved snapshot or that the device must be connected.

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