rubeus_ptt

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

No annotations are provided, so the description must fully convey behavior. It mentions importing a ticket and enabling access, but does not disclose side effects like ticket replacement, permission requirements, or error scenarios. It lacks detail for a security-sensitive operation.

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?

Two concise sentences: the first states the purpose and the second explains the mechanism. No redundancy, front-loaded key 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 action and input, but lacks details on output (e.g., success/failure indication) and potential errors. Given no output schema, more information would help an agent handle the tool 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?

The input schema already provides high-coverage descriptions for both parameters (ticket format, luid elevation). The tool description does not add additional meaning beyond what is in the schema, so baseline score applies.

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 passes a Kerberos ticket to the current session, specifying the action, input format, and result. It distinguishes itself from sibling tools like rubeus_asktgt or rubeus_golden by focusing on applying an existing ticket.

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 when you have a Kerberos ticket to use, but does not explicitly state when to avoid this tool or mention alternatives. It is self-explanatory within the context of sibling tools with distinct purposes.

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