ad_psexec

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

No annotations are provided, so the description must disclose behavioral traits. It only states that commands are executed, without mentioning authentication requirements, potential destructiveness, output behavior, or error handling. This is insufficient for a command execution tool.

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 a single sentence followed by a parameter list. It is front-loaded with the purpose. However, the parameter list could be better formatted (e.g., using a table or clearer typography) to improve readability.

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 6 parameters, no annotations, and the presence of sibling tools, the description is incomplete. It does not mention the output format, return values, error scenarios, or how to handle authentication (e.g., password vs hash). The output schema exists but is not described, leaving gaps.

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 description lists all six parameters with brief descriptions, compensating for the 0% schema coverage. However, the descriptions are minimal (e.g., 'Username' for username, 'NTLM hash for pass-the-hash' for hashes) and do not add rich semantic meaning beyond the parameter names.

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 executes commands on a remote Windows host via PsExec (impacket). It is specific about the verb and resource. However, it does not distinguish from sibling tools like ad_wmiexec, which also executes commands remotely, so it lacks sibling differentiation.

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?

No guidance on when to use this tool versus alternatives (e.g., ad_wmiexec, ad_secretsdump). No prerequisites or context for appropriate usage are provided.

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