websex_john

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that john is executed directly with argv tokens and no shell parsing, and that it runs from the engagement namespace with relative paths. However, it omits operational details such as expected resource usage, execution duration, output behavior, or safety considerations for a potentially long-running cracking process.

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 three short sentences and front-loads the primary action. The execution detail and path guidance are useful, and there is no filler. It could be slightly more structured by grouping parameter-related guidance, but it is appropriately sized.

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 tool's complexity (arbitrary binary execution via argv) and the existence of an output schema, the description does not need to explain return values. However, with 0% schema description coverage and no annotations, it should say more about stdin, working directory semantics, and when an agent should choose this over sibling credential tools. It provides useful execution context but is not fully complete.

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. It clarifies that 'arguments' are argv tokens passed directly to john, that 'engagement_id' selects the engagement namespace, and that relative paths should be used for artifacts. It does not explain the 'stdin' parameter or the exact role of 'working_directory' beyond the path guidance, leaving gaps for two of four parameters.

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 states a specific verb and resource: 'Run john from the WebSex credentials toolkit.' It is clear that this executes the John the Ripper password cracker, but it does not explicitly differentiate itself from sibling credential tools like websex_hashcat, websex_hydra, or websex_ophcrack.

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 such as hashcat or hydra. The mention of the credentials toolkit implies a domain, but there are no explicit conditions, prerequisites, or exclusions to help an agent choose correctly.

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