analyze_rdp_attack_chain

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It discloses the core behavior (correlates, extracts hints) but lacks details on whether it is read-only, what 'forensic hints' entail, or any limitations. For an analysis tool, this is adequate but not rich.

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, two sentences, with the core purpose front-loaded. The Chinese prefix adds a stylistic element but does not harm clarity. Every sentence contributes meaningful information.

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 four parameters, no output schema, and no annotations, this description is too brief. It does not explain the output format (e.g., what forensic hints look like) or whether one input is preferred over the other. Given the complexity of RDP/NTLM attack chain analysis, more context is needed.

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 covers all parameters with descriptions, so the baseline is 3. The description adds the key alternative between session_id and pcap_path, but does not elaborate on max_packets or auto_correlate, which are already well described in the schema.

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 identifies the tool's purpose: automated analysis of the RDP + NTLM attack chain, with explicit correlation of NTLM evidence with RDP sessions and extraction of forensic hints. This distinguishes it from sibling tools like analyze_lateral_movement or extract_ntlm_hashes by focusing specifically on the combined RDP/NTLM chain.

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 implies when to use the tool (when investigating RDP/NTLM attack chains) and mentions two accepted input modes (session_id or pcap_path). However, it does not explicitly state when not to use it or what alternatives might be preferable, such as analyze_lateral_movement for broader lateral movement analysis.

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