frida_java_choose

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

The description lacks any behavioral information beyond the tool name. It does not disclose whether the tool lists instances, modifies state, requires specific permissions, or has side effects. With no annotations to supplement, this is a critical gap.

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?

While the description is extremely short (3 words), it sacrifices essential context. Conciseness should not come at the expense of clarity. The one-line sentence provides no structure or additional value, making it minimal to the point of being uninformative.

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?

Given the lack of output schema, no annotations, and a high number of sibling tools, the description is wholly inadequate. An agent cannot determine the tool's purpose, return format, or how it integrates with other Frida operations. The description fails to bridge the gap left by missing structured metadata.

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 schema has 4 parameters with no descriptions, and the tool description adds no information about them. The agent cannot infer what 'target', 'class_name', 'limit', or 'duration_seconds' mean from the description alone. This forces reliance on the schema titles, which are insufficient.

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 'Call Java.choose()' restates the tool name without explaining what Java.choose() does or how it differs from sibling tools like frida_java_hook_method or frida_java_call. It assumes prior knowledge of Frida's Java API, making it vague for an AI agent unfamiliar with the specific function.

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 guidance is provided on when to use this tool versus alternatives. There are many related sibling tools (e.g., frida_java_hook_method, frida_java_list_classes), but the description does not indicate scenarios where Java.choose() is appropriate, nor does it mention prerequisites or limitations.

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