rubeus_createnetonly

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

No annotations are provided, so the description carries the full burden. It discloses that 'The process can be hidden or visible,' which is a behavioral trait. However, it does not mention other important details like whether the tool requires administrative privileges, what happens to the parent process, or if network credentials are stored. Some behavioral information is given but not comprehensive.

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 consists of three brief, front-loaded sentences. The first sentence states the core purpose, the second explains the utility, and the third adds a behavioral detail. No redundant or irrelevant information. Every sentence earns its place.

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 complexity (6 parameters, no output schema, many sibling tools), the description provides a good overview: purpose, use case, and a behavioral option. However, it does not explain the 'logon type 9' concept or clarify behavior when parameters like 'ticket' are omitted. Still, for an agent familiar with Rubeus, it is largely sufficient.

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 100%, so the baseline is 3. The description adds only one meaningful elaboration: 'The process can be hidden or visible,' which relates to the 'show' parameter. For other parameters, the description does not add beyond what the schema already specifies (e.g., 'Ticket to apply to new process' is already in the schema description). Limited additional semantic value.

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 action: 'Create a new process with network credentials (logon type 9).' It identifies the resource (a new process) and the specific context of network credentials and applying tickets, which differentiates it from sibling tools like rubeus_ptt (injects into current process) or rubeus_s4u (impersonation). No ambiguity.

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 explains when to use the tool: 'Useful for applying tickets to a separate process.' However, it does not provide explicit guidance on when not to use it or mention alternative tools (e.g., rubeus_ptt for immediate ticket injection). The usage context is clear but lacks exclusions or comparisons.

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