ad_psexec

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. The one-word description reveals nothing about side effects, authentication requirements, or whether it is a read-only or destructive operation. This is a critical gap for a tool that executes code on remote Windows hosts.

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 extremely short, but this is under-specification rather than conciseness. It conveys zero information about the tool's functionality, so the brevity is not a virtue.

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?

With four required parameters, no annotations, and no output schema, the description is wholly inadequate. It provides no context about execution behavior, expected outputs, or any caveats, making it impossible for an agent to use the tool correctly without external knowledge.

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 schema description coverage is 0% and the description adds no meaning to the parameters. The fields domain, username, password, and target are present in the schema but their purpose and format are completely unexplained, leaving the agent without guidance.

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 is simply 'PsExec.' which merely restates the tool name without any verb or resource. It doesn't indicate whether this tool executes commands, manipulates processes, or manages remote Windows systems, and it fails to distinguish from sibling tools like ad_wmiexec or ad_evil_winrm.

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?

There is no guidance on when to use this tool versus alternatives. No mention of scenarios, prerequisites, or comparisons to sibling AD execution tools.

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