frida_win_etw_bypass

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

With no annotations, the description carries the burden. It explains the patching behavior and return value, but lacks disclosure of side effects (e.g., reversibility, persistence, required privileges) or the impact on the process. This is adequate for a simple patch but leaves potential risks unaddressed.

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 front-loaded with a one-line summary of the purpose, followed by concise technical details. Every sentence adds value, and the format is clean and scannable.

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?

The description covers the core functionality but omits prerequisites (e.g., must be attached to a process via Frida), expected state before invocation, and whether the patch is per-session or persistent. Given the tool's simplicity and lack of output schema, it is moderately complete but leaves gaps for an agent to infer.

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 input schema has 0% coverage for parameter descriptions, so the description adds essential meaning: 'target: process name or pid (string).' This clarifies the parameter's purpose beyond the type definition, enabling correct agent usage.

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 tool's purpose: 'Patch EtwEventWrite to neutralise ETW event logging' on Windows. It specifies the mechanism (overwriting with xor eax,eax; ret) and context (standard anti-logging bypass), distinguishing it from sibling bypass tools like frida_win_amsi_bypass.

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 Windows usage and mentions target as process name/pid, but does not explicitly state when to use this tool versus alternatives (e.g., AMSI bypass) or when not to use it. No prerequisites or exclusion criteria are provided, relying on implicit context.

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