websex_hashcat

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

With no annotations, the description must carry the whole behavioral burden. It usefully discloses that hashcat is invoked directly with argv tokens and that shell parsing is never used — a security-relevant execution guarantee — plus the engagement-namespace working context. It omits anything about resource intensity, runtime duration, potfile/session side effects, or failure behavior for such a compute-heavy 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?

Three compact sentences, front-loaded with what the tool is, then the execution semantics, then the path convention. Little waste; each sentence adds information rather than restating the name.

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?

An output schema exists, so return values needn't be explained, and the execution model is covered. What is missing for an arbitrary-argv wrapper around a heavy cracking binary is guidance on when it is the right tool relative to its siblings, and any warning about cost/duration.

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 description coverage is 0%, so the description should compensate. It explains that 'arguments' are raw argv tokens and that 'working_directory' accepts relative paths in the engagement namespace, covering two of four params, but 'stdin' and 'engagement_id' get no explicit semantics beyond the general namespace remark.

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?

States a specific verb and resource — run hashcat — and situates it in the WebSex credentials toolkit, so the agent knows exactly what binary will execute. It does not distinguish itself from close siblings like websex_john, websex_ophcrack, or websex_hash_identifier, but the purpose itself is unambiguous.

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 gives operational context (runs from the selected engagement namespace, use relative paths for artifacts) but never says when to reach for hashcat versus the sibling crackers john/ophcrack or the identifier tool. Usage is only implied by the 'credentials toolkit' framing.

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