ad_kerberoast

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

No annotations are provided, and the description gives zero behavioral details. The agent learns nothing about what the tool does to the target, whether it requires network access, what credentials it needs, or what output it produces. This is a complete failure to disclose behavior beyond the tool's name.

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 technically short but this is under-specification, not conciseness. A single vague term does not earn its place; it fails to provide even a basic explanatory sentence. It is too minimal to be considered well-structured.

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 that Kerberoasting is a complex offensive security technique with no annotations, no output schema, and no parameter explanations, the description is completely inadequate. It lacks context about the attack method, expected results, or any operational details, leaving the agent with no way to invoke it correctly.

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?

With schema description coverage at 0% and the description offering no information about domain, username, or password, the agent has no understanding of what these parameters mean or how they should be formatted. The description adds nothing beyond the raw schema.

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 is simply the word 'Kerberoasting,' which restates the tool name without providing a specific verb or resource. It doesn't clarify what the tool actually does, such as extracting Service Principal Names or performing an AS-REP roast, and fails to distinguish it from sibling AD tools.

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?

There is no guidance on when to use this tool versus alternatives like ad_asreproast or ad_secretsdump. The description provides no context for appropriate deployment, prerequisites, or scenarios where this tool is preferred, leaving agents without any usage direction.

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