blackdex_prepare

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

With no annotations, the description carries the full burden. It usefully discloses that an APK path is required and that a manual on-device step follows, but it says nothing about return values, error behavior, or whether the device serial/adb connection must already be established. Partial behavioral context only.

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?

Two tight sentences that front-load the core action before the follow-up note. No wasted text, though the trailing on-device instruction is more workflow guidance than an invocation directive.

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 preparation tool with no annotations and no output schema, the description covers the essential step and the manual follow-up, but omits prerequisites (device must be listed/connected), the meaning of serial, and what success produces. Adequate but with clear gaps.

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 50%: blackdexApkPath is documented in both schema and description ('需提供其 APK 路径'), but the serial parameter is undocumented in the schema and untouched by the description. The description also does not explain how serial interacts with 'on the device'.

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 names a concrete action ('在设备安装并启动 BlackDex', install and launch BlackDex on the device) and scopes itself as the first step of the no-root unpacking path, which distinguishes it from blackdex_pull and the frida_* siblings. The verb+resource is specific enough that an agent knows this is a setup stage rather than the actual unpacking.

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?

It signals ordering ('免 root 方案第一步') and what comes next (manually select the target app to unpack), which gives implied usage context. However, it never names the alternative path (frida_prepare) or states prerequisites/exclusions, so the agent must infer when to choose this over the rooted workflow.

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