extract_ntlm_hashes

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

With no annotations provided, the description carries the full burden. It discloses input modes and output formats but does not reveal whether the operation is read-only, what the return value looks like, prerequisites like a loaded PCAP, or limitations. This is a significant gap for a tool with zero 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 a single sentence with a concise tag prefix that immediately front-loads the purpose. Every phrase earns its place, and there is no redundant verbiage.

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 has 4 parameters and no output schema, the description lacks critical contextual details such as the return format of extracted hashes, prerequisites (e.g., needing a loaded PCAP), and behavior when both session_id and pcap_path are supplied. The presence of sibling tools further underscores the need for clearer usage boundaries.

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 baseline is 3. The description adds minimal value by saying 'Accepts session_id or pcap_path', slightly clarifying the alternative inputs, but the schema already documents these parameters. No additional parameter semantics are provided.

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 a specific verb 'Extract' and a specific resource 'NTLM hashes from SMB/RDP authentication traffic'. It also mentions output formats (Hashcat, John), which distinguishes it from more generic tools like extract_credentials.

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 context by specifying the target traffic (SMB/RDP) and input modes (session_id or pcap_path), but it does not explicitly state when to choose this tool over siblings like extract_credentials or decrypt_rdp, nor does it mention exclusions or alternatives.

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