trace_jni_callbacks

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

No annotations are supplied, so the description carries the full behavioral burden, and 'Alias for trace_jni_upcalls' discloses nothing about mutation, permissions, side effects, or output. The one useful implication is that behavior matches trace_jni_upcalls, but that requires the agent to look up another tool.

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 short sentence is front-loaded and wastes no words, which is the right shape for an alias. Its problem is under-specification rather than verbosity, so it scores as structurally adequate but content-thin.

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 tool with three undocumented parameters, no annotations, and no output schema, one line of aliasing text is far from enough. An agent cannot determine what so_name, apk_path, or fn_offset mean, nor what the tool returns, without opening the sibling tool's definition.

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 0% and three parameters (so_name, apk_path, fn_offset) are completely undescribed in both the schema and the description. The description adds no meaning at all — notably it never explains the format of fn_offset or when apk_path is required.

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 only asserts that this is an alias for trace_jni_upcalls, so the agent must infer the actual verb and resource from the sibling's name. It never states that it traces JNI callbacks, and given siblings like trace_jni_upcalls and get_cross_boundary_slice, the alias relationship is the only distinguishing signal provided.

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?

Calling it an 'alias' weakly implies it can be used interchangeably with trace_jni_upcalls, but there is no explicit when-to-use, when-not-to-use, or reason to prefer one name over the other. The agent is left to guess whether this is a deprecated name, a compatibility shim, or behaviorally identical.

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