rubeus_asktgt

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

The description explains that the TGT can be saved to a file, applied to the current session (PTT), or returned as base64. It lists multiple authentication methods and flags like opsec. Without annotations, it carries the full burden but does not discuss side effects or error conditions.

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 bullet points and example use cases, conveying essential information without unnecessary verbosity. Every sentence adds value.

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 17 parameters and no output schema, the description covers authentication methods, output options, and use cases adequately. It could mention prerequisites like domain controller connectivity or error handling, but overall is fairly complete.

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 baseline is 3. The description adds value by grouping authentication methods (password, hash, certificate) and providing context for output options (outfile, ptt) through example use cases, exceeding the schema-only information.

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 requests a Ticket Granting Ticket (TGT) using user credentials. It distinguishes from sibling tools like rubeus_asktgs (which requests service tickets) by focusing on TGT acquisition.

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 includes example use cases (lateral movement, test credential validity, support subsequent ticket operations) that indicate when to use the tool. However, it does not explicitly state when not to use or mention alternatives among sibling tools.

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