john_the_ripper

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'cracking hashes', implying a write or destructive operation, but doesn't specify permissions, rate limits, or output behavior. The description lacks details on what happens during cracking, such as success/failure states or timeouts, making it insufficient for a tool with no annotation coverage.

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 concise and front-loaded with a single sentence: 'cracking hashes using john based on format and a wordlist'. It wastes no words, though it could benefit from more structure or elaboration given the tool's complexity. It's appropriately sized but slightly under-specified.

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 (hash cracking with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter details, or usage context, making it inadequate for an AI agent to reliably invoke the tool. More information is needed to compensate for the missing structured data.

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 mentions 'format and a wordlist', which maps to two of the three parameters, but doesn't explain 'hashfile' or provide details on parameter usage, such as format examples or wordlist paths. The description adds minimal value beyond the schema, failing to fully address the coverage gap.

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 states the tool's purpose: 'cracking hashes using john based on format and a wordlist'. It specifies the verb ('cracking'), resource ('hashes'), and method ('using john'), though it doesn't explicitly differentiate from sibling tools like 'dump_sam_hashes' or 'Kerberoast' which might also handle hashes. The purpose is clear but lacks sibling distinction.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a hashfile or specific formats, or compare it to sibling tools like 'get_john_formats' or 'generate_pwd_wordlist'. Usage is implied but not explicitly stated, leaving gaps for an AI agent.

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