rubeus_changepw

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

Without annotations, the description carries the full burden. It mentions using a TGT, the Kerberos Set Password protocol, and targeting other users with permissions. However, it does not disclose potential side effects, authentication requirements, or whether the operation is destructive. The phrase 'just their TGT' is ambiguous.

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 three sentences, concise and front-loaded with the main action. It could be slightly more structured (e.g., separate bullet for permissions) but is efficient overall.

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 no output schema and the tool's security-sensitive nature, the description should explain return values, success/failure indications, and prerequisites. It lacks information on what happens after the password change, and the complexity of Kerberos protocols warrants more context.

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% (all 5 parameters have descriptions). The description restates the target user capability but adds no new semantic information beyond the schema. Baseline 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 changes/resets a user's password using a TGT via the Kerberos Set Password protocol. It specifies the verb (change/reset) and resource (password), and the technique is distinct from sibling tools like rubeus_asktgt or rubeus_kerberoast.

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 TGT and want to change a password, including targeting other users with permissions. However, it lacks explicit guidance on when not to use it, prerequisites beyond a TGT, or alternatives like using a service ticket.

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