john

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

No annotations are provided, so the description carries the full burden. It discloses that john is offline, CPU-based, supports auto-detection, and states the output format. It does not mention resource consumption or runtime expectations, but for a cracking tool the key operational traits are covered.

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 compact and front-loaded: identity, purpose, use cases, alternative, and output appear in a logical order with no filler. Every sentence contributes either selection guidance or invocation context.

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?

For a tool with no annotations and no output schema, this description covers purpose, when to use it, when not to use it, operational constraints, and output. Minor gaps like runtime expectations or the exact behavior of auto-detection remain, but the essential information for correct selection and invocation is present.

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 100%, so the schema already documents all four parameters. The description adds context about hash sources and output, but it does not add substantive parameter-level meaning beyond what fmt/wordlist/opts descriptions already provide.

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: 'offline password hash cracker.' It names concrete sources (/etc/shadow, SAM, captured network hashes), lists hash format support, and explicitly contrasts itself with the sibling tool hashcat, so an agent can distinguish it without reading schemas.

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 explicit when-to-use guidance: cracking offline hashes from shadow/SAM/network sources, and CPU-based cracking for smaller sets. It also names the alternative, hashcat, for GPU-accelerated large sets. This is clear routing among siblings.

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