impacket_kerberoast

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

With no annotations provided, the description carries the burden. It discloses that the tool makes TGS requests (network behavior), warns about EDR/SIEM detection, notes password redaction in logs, and requires an allowed host – all useful behavioral context. It does not detail side effects or error scenarios, but the key risk is covered.

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 well-structured with a clear introductory sentence, an Args section that is concise, a Returns note, and a WARNING section. No redundant text; each sentence provides necessary 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?

The description covers the core function, expected outputs (service accounts, SPNs, TGS hashes), and important warnings (detectability, credential requirement, allowed hosts). However, it does not explicitly state that either password or hashes must be supplied (both are optional in the schema) or clarify the default timeout value. Given the output schema exists, this is adequate but not exhaustive.

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 schema has zero descriptions (0% coverage), but the description explains every parameter: target (DC IP), domain (AD domain), username (valid domain user), password (authentication), hashes (NTLM format LM:NT, alternative), and timeout (override default). This fully compensates for the schema gap.

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 it performs Kerberoasting using Impacket GetUserSPNs, specifically requesting TGS tickets for service accounts with SPNs. This distinguishes it from sibling tools like impacket_secretsdump or psexec.

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?

It outlines prerequisites (valid domain credentials, allowed target) and the outcome (offline-crackable hashes), but does not explicitly compare against alternatives or state when not to use it. The usage context is implied rather than fully specified.

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