adb_extract_apks

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

No annotations are provided, so the description carries the burden. It states the tool pulls APK splits, implying a read operation. It does not disclose error handling (e.g., missing package) or overwrite behavior, but the simple action is clear. A score of 4 reflects adequate transparency for a read-only 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: first defines the action, second states use cases. No extraneous words, efficiently conveying purpose and context.

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 tool lacks an output schema, but the description sufficiently explains the operation. It could mention that the tool returns success or file paths, but given its simplicity and clear purpose, it is mostly complete.

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 baseline is 3. The description adds context by saying 'from the device to a local directory', mapping to outputDir, but does not provide additional parameter details beyond what the schema offers.

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 'Pull all APK splits for a package', which specifies the verb and resource. It distinguishes from siblings like adb_pull (generic file pull) and adb_install by focusing on APK splits.

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 mentions it is useful for analysis, backup, or transfer, but does not specify when to avoid using it or provide explicit alternatives. Among siblings, adb_pull could also retrieve APK files, but the tool specifically handles splits. No prerequisites or limitations are stated.

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