ad_evil_winrm

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

With no annotations, the description must disclose behavior itself. It only states 'WinRM shell' without explaining that it performs remote authentication, establishes an interactive session, or may have security/network implications. Minimal useful behavior is implied but not elaborated.

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 a single short phrase with no filler, but it is severely under-specified. True conciseness would still include essential usage context; this is under-specification, not concise efficiency.

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?

This is a remote shell tool with no annotations, no output schema, and four undocumented parameters. The description is only a name label and fails to convey prerequisites, return behavior, or additional_args semantics, making it incomplete for reliable invocation.

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 0% with no descriptions on any property. The description adds no meaning to target, username, password, or additional_args, leaving the agent to guess what each parameter does.

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 identifies the tool as providing a WinRM shell via evil-winrm, which is a specific verb+resource. It distinguishes from siblings like ad_psexec and ad_wmiexec by naming the WinRM protocol, although it's terse.

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 provides zero guidance on when to use this tool versus alternatives. No scenario, prerequisites, or exclusions are mentioned, leaving the agent to infer from the name alone.

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