bossix_hide

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

With no annotations, the description carries the transparency burden. It explicitly details the patches applied (zero BeingDebugged, clear NtGlobalFlag, x64dbg built-in hide), giving concrete behavioral insight. It does not mention side effects or reversibility, but the core destructive actions are well disclosed.

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 a single sentence that front-loads the action and provides essential technical details. Every word earns its place, with no fluff or redundant information.

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 zero-parameter utility, the description is sufficiently complete, covering what it does and how. The existence of an output schema fills in return-value details. It lacks explicit prerequisites (e.g., must be attached to a debuggee), but given the low complexity, this is a minor gap.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific information, but that is acceptable since no parameters need explanation. The schema itself covers the empty parameter set fully.

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 uses a specific verb ('Hide') and resource ('debugger via PEB patches'), and enumerates concrete techniques ('zero BeingDebugged, clear NtGlobalFlag, x64dbg built-in hide'). This clearly distinguishes it from sibling tools like bossix_scan or bossix_patch while making the tool's function immediately obvious.

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 in anti-debugging contexts but provides no explicit when-to-use guidance or references to alternatives. It does not state when not to use it or mention prerequisites, which is a gap for a tool that manipulates process internals.

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