frida_kernel_alloc

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

No annotations exist, and the description fails to disclose any behavioral traits such as whether the allocation is destructive, side effects, permission requirements, or failure modes. The agent has no insight beyond the function name.

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 extremely brief, the description is under-specified. It lacks necessary details about the tool's behavior and parameters, making it more 'insufficient' than '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?

Given the tool has one parameter and no output schema, the description should explain what Kernel.alloc does, how the size parameter affects behavior, and what the return value represents. It provides none of this.

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 adds no meaning to the 'size' parameter. With 0% schema description coverage, the agent must guess the format, units, or constraints (e.g., size range, alignment). The description is completely silent.

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 Kernel.alloc()' is essentially a tautology of the tool name. It does not explain that it allocates kernel memory or distinguish it from similar tools like frida_memory_alloc, which allocates user-space memory.

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 (e.g., frida_memory_alloc, frida_kernel_read). The description offers no context about prerequisites or typical use cases.

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