rubeus_dump

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

With no annotations, the description discloses key behaviors: extraction from current or all sessions (with elevation) and output format (base64 kirbi). It does not mention side effects or detailed auth requirements, but is relatively transparent.

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?

Three sentences: first states purpose, second explains scope, third describes output format. No wasted words, front-loaded with core action.

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 primary behavior and output, but lacks guidance on parameter combinations (e.g., when to use filters). For a dump tool, it is fairly complete but could benefit from a usage note.

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 each parameter described briefly (e.g., 'Target specific LUID'). The tool description adds no further parameter context beyond the schema, so a baseline score of 3 is appropriate.

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 dumps Kerberos tickets from memory (current or all sessions). It distinguishes from sibling tools like rubeus_klist and rubeus_ptt by focusing on extraction rather than listing or injection.

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 for extracting tickets, mentioning elevation for all sessions, but does not explicitly advise when to use alternatives or provide exclusions. Among many sibling tools, some guidance would be helpful.

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