websex_ophcrack

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

With no annotations, the description carries the full burden, and it does disclose real execution semantics: the container runs `ophcrack` directly with argv tokens and shell parsing is never used (a meaningful command-injection safety note), plus the namespace/path scoping behavior. It stops short of stating timeout, resource cost, or whether artifacts are modified.

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 sentences, front-loaded with purpose, then execution semantics, then scoping. No filler, though it could be tightened.

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 need not be described. For a 4-parameter exec wrapper the description covers purpose, argv handling, and engagement scoping, but omits stdin semantics and any invocation constraints, leaving a modest gap.

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 must compensate, and it partially does: it clarifies `arguments` as argv tokens (no shell interpretation) and ties `working_directory` to relative engagement paths. It says nothing about `stdin` or the exact role of `engagement_id`, leaving one of four parameters unexplained.

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 concrete verb+resource (\"Run ophcrack...\") and it is a uniquely named tool, so an agent knows exactly which binary is invoked. However it gives no differentiation from sibling password crackers such as websex_john, websex_hashcat, or websex_hash_identifier, so the agent cannot tell why ophcrack rather than one of those.

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?

Provides operational context (runs from the selected engagement namespace, use relative paths for engagement artifacts) but never states when to choose this over the other credential-cracking siblings. Usage is implied by the tool name rather than argued.

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