frida_android_jni_hook

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

Discloses that the tool captures arguments and return values and hooks into libart.so. No annotations provided, so description carries burden. However, does not mention if hooks persist, require cleanup, or impact performance. Adequate but not comprehensive.

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?

Description is brief (4 lines) and front-loaded with purpose. Listing examples of hooked functions is helpful. Could be slightly more structured, but efficient.

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?

Covers purpose and parameters, but lacks output format details (since no output schema) and behavioral context like permissions or runtime requirements. Adequate for a simple hook tool but not fully 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?

Adds meaning beyond schema: clarifies target as process name or pid, function_name with examples (RegisterNatives, FindClass), and duration_seconds default 10. Schema coverage 0%, so description compensates well.

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?

Clearly states the tool hooks JNI functions in libart.so, listing specific functions like RegisterNatives and FindClass. Uses specific verb 'hook' and resource 'JNI functions', which distinguishes from sibling tools like frida_android_content_provider_hook or frida_android_webview_hook.

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 explicit guidance on when to use this tool versus alternatives such as frida_java_hook_method or frida_hook_native_function. Does not mention prerequisites, context, or when not to use.

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