adb_snapshot_capture

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

No annotations provided; description says 'saves to a JSON file' but does not specify file location, overwrite behavior, or whether the operation is read-only. The potential side effects or permissions needed are not disclosed.

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 sentence with essential information, avoiding unnecessary details. It is efficiently structured but could be slightly more precise.

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?

No output schema; description only vaguely mentions 'comprehensive device state' without detailing the JSON structure or contents. Lacks information on how to retrieve the saved file and what specific data is captured, which is insufficient for a snapshot tool.

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 descriptions for both parameters (name and device). The description adds no extra meaning beyond the schema, so baseline score of 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 the tool captures a comprehensive device state snapshot including packages, settings, and system properties, and saves to a JSON file. This distinguishes it from siblings like adb_getprop (only properties) or adb_list_packages (only packages).

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 guidance on when to use this tool versus alternatives (e.g., adb_snapshot_compare, adb_device_info). The description lacks context on prerequisites or typical use cases.

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