deobfuscate_jni_strings

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses essentially nothing about behavior. By calling itself an alias it implies parity with extract_jni_onload_strings, which weakly signals a read-only extraction, but it says nothing about what is read (a .so, an APK), whether anything is mutated, or what happens when the target is absent.

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 single sentence is front-loaded and free of padding, and the alias statement is the most useful fact available. However, the brevity is a symptom of under-specification rather than disciplined editing, since nearly everything an agent needs is absent.

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?

With no annotations, no output schema, and zero parameter documentation, the description would need to do substantial work to make this tool callable, and it does almost none. A caller cannot determine the required path vs. name relationship or the return shape from this definition alone.

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 description coverage is 0% and the description adds no parameter meaning whatsoever. It leaves both so_name (required) and apk_path undocumented, including the crucial question of whether apk_path is an optional locator for the .so or a required alternate input mode.

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 identifies the tool only as an alias for extract_jni_onload_strings, so an agent must already know what that sibling does to infer this tool's job. The redirect does differentiate it from unrelated siblings like sync_ida_jni_types, but it never states a verb or resource in its own right (e.g., that it pulls obfuscated strings out of a .so).

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?

There is no guidance on when to call this versus extract_jni_onload_strings, which is the only meaningful alternative for an alias. An agent cannot tell whether the two are fully interchangeable, whether one is preferred, or whether calling both is redundant.

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