crypto_ntlm

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

No annotations are provided, and the description does not disclose the input format, output structure, or any side effects. The tool likely expects a password string, but this is not specified. The agent has little insight into behavior beyond hash generation.

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 relatively short but includes redundant phrases like 'NTLM Hash Generation' and 'Generate NTLM and LM password hashes'. It could be more concise, but it is not overly verbose.

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 lack of parameter definitions and output schema, the description is incomplete. It directs to describe_tool for more guidance, indicating that the current description alone is insufficient for effective tool use.

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?

The input schema has no defined parameters but allows additional properties. The description does not explain what properties to provide (e.g., password field). Despite high schema coverage, the description adds no value for parameter semantics.

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 generates NTLM and LM password hashes for Windows authentication, with specific contexts like Active Directory and penetration testing. This is a specific verb-resource pair that distinguishes it from sibling crypto tools.

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 clear context for when to use the tool (Windows authentication, pen testing, security analysis). It does not explicitly state when not to use it or mention alternatives, but the context is sufficient for a typical agent.

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