blackdex_pull

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

With no annotations, the description carries the full burden; it does disclose the operation is a device-to-host transfer over previously dumped dex output, which is useful non-obvious context. It omits whether the pull is read-only or overwrites, how files are named/placed, and what happens if no dump exists.

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?

A single sentence, front-loaded with the pipeline position (‘第二步’) and the operation, with zero redundant or filler text.

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 3-parameter tool with no annotations, no output schema, and 0 required parameters, the description is thin: it never says what is produced (file list? paths?), what outDir/serial control, or what error conditions mean. An agent could pick this tool but not call it confidently.

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 only 33% (only targetPkg is described in the schema) and the description never mentions outDir or serial. The implied destination ('拉回本机') is the closest it comes to explaining outDir, so it does not compensate for the coverage gap.

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 gives a specific verb (拉回/pull) and resource (BlackDex 脱壳 dump 出的 dex) plus the data-flow direction (from device to local machine). It is distinguishable from siblings like pull_apk or frida_unpack because it names BlackDex specifically, though it never explicitly contrasts itself with them.

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?

"免 root 方案第二步" implies it must run after blackdex_prepare, which is genuine sequencing guidance. However, there is no explicit statement of prerequisites (device connected, dump already performed) nor any when-not/alternative routing versus pull_apk or frida_unpack.

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