frida_java_load_dex

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

The description explains the mechanism (Java.openClassFile().load()) and the outcome (classes available via Java.use()). However, with no annotations, it lacks details on side effects (e.g., is it reversible?), error conditions, or whether it can be invoked multiple times.

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 concise at four sentences, with the purpose stated first, followed by implementation detail, effect, and parameter clarification. Each sentence adds value, though the third sentence could be slightly more concise.

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 simple load action with three parameters and no annotations, the description covers purpose, mechanism, and two parameters. It lacks information on return values, error handling, or prerequisites (e.g., an active Frida session). Some important context is missing, making it minimally adequate.

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?

The description provides meaningful explanations for two of three parameters: 'target' is clarified as process name or PID, and 'dex_path' as a filesystem path. The third parameter, 'device_id', is not mentioned, leaving a gap. Given 0% schema coverage, this is a significant but incomplete contribution.

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 the verb ('load') and resource ('DEX file'), and specifies the context ('into an Android process at runtime'). It differentiates from sibling tools like frida_java_hook_method by focusing on loading a DEX file.

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 implies usage by describing the underlying API call and its effect, but it does not explicitly state when to use this tool versus alternatives (e.g., when to load a DEX vs hooking methods directly). No guidance on prerequisites or preconditions.

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