nmap_scan_to_file

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

The description discloses a non-trivial workflow (write → check → append), which adds behavioral context beyond the tool name. However, it omits important details such as file path, overwrite behavior, permission requirements, or potential side effects. Without annotations, more transparency would be beneficial.

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 very short (one line), which is concise but lacks essential information about parameters and usage. It front-loads the workflow but sacrifices completeness.

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 5 parameters, a required input, and an output schema, the description fails to cover what the parameters do or when to use the tool. The output schema existence mitigates missing return value info, but overall the description is insufficient for effective tool selection and invocation.

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%, and the description does not explain any of the 5 parameters (target, options, label, sudo, timeout). Users cannot infer their meaning or usage from the description alone.

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 'write scan results to file → read verification → append again' clearly conveys a multi-step process involving writing, checking, and appending to a file. It distinguishes from sibling tools that output to stdout or specific formats (e.g., nmap_scan_json, nmap_quick_scan) by emphasizing file I/O with verification.

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?

No guidance is provided on when to use this tool versus siblings. For example, it does not explain when to prefer this over nmap_scan or nmap_scan_json, nor does it mention prerequisites or typical use cases.

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