rubeus_tgtdeleg

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

With no annotations provided, the description carries full burden. It discloses that the tool uses Kerberos GSS-API, abuses delegation, and works with standard permissions. However, it does not detail potential side effects or network requests, though as a read-only extraction tool, the transparency is adequate.

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 concise with four sentences, front-loaded with the main purpose, followed by key technical details and use cases. No unnecessary words; 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 the tool's complexity and lack of output schema, the description is largely complete: it explains what the tool does, its advantage (no elevation), and the resulting artifact (TGT for pass-the-ticket). However, it could mention how to inject or use the extracted TGT, but overall it's sufficient for advanced users.

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 both parameters described in the input schema. The description adds no new meaning beyond restating that 'target' is the target SPN for delegation and 'nowrap' controls base64 wrapping. Thus, parameter semantics score is baseline 3.

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 'extracts a usable TGT for the current user without elevation,' providing a specific verb and resource. It references the 'tgt::deleg' technique from Kekeo, distinguishing it from other Rubeus tools like asktgt or asktgs.

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 mentions no elevation is required and that the TGT can be used for pass-the-ticket, but it lacks explicit guidance on when to use this tool versus alternatives like asktgt or s4u. The context is implied rather than explicitly stated.

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