rubeus_asreproast

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explains that the AS-REP response contains encrypted data with the user's password hash, but omits critical details such as required permissions, side effects (if any), stealthiness, rate limits, or any consequences of using the 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 description is front-loaded with the core purpose in the first sentence, followed by concise bullet points. It is efficient but slightly verbose with repeated details; overall no wasted content.

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's complexity (12 parameters, no output schema), the description covers the main use case but lacks details on return values, typical output examples, and behavior under different scenarios. It is adequate but not comprehensive.

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% with parameter descriptions, so the baseline is 3. The description adds context for a few parameters (output format, OU targeting) but does not explain others like creduser, des, or ldapfilter beyond what the schema already provides.

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 performs AS-REP Roasting against accounts lacking Kerberos preauthentication, specifies the target vulnerability, and lists features like per-user targeting, output formats, and OU filtering. This distinctively differentiates it from siblings like rubeus_kerberoast.

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 for accounts with 'Do not require Kerberos preauthentication' enabled, but does not explicitly compare with sibling tools or provide when-not-to-use guidance. No exclusion criteria or prerequisites are mentioned.

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