pentest_recon_portscan

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

With no annotations, the description carries the full burden. It does disclose the meaningful trait that the scan performs full TCP connects (as opposed to a SYN scan), but says nothing about noise/detectability, expected duration, what a result looks like, or how out-of-scope or unreachable targets are handled.

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?

Two short sentences, front-loaded with the scan type and immediately followed by the one non-obvious parameter format. No filler or redundancy.

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 four-parameter network scanner with no annotations and no output schema, the definition is only minimally sufficient. The port syntax is covered, but the timeout and concurrency semantics and the shape of the response (presumably open ports) are left for the agent to infer.

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%, so the description must compensate. It does document the 'ports' syntax well with three concrete formats ('top', '22,80,443', '8000-8100'), but leaves target, timeout, and concurrency entirely unexplained, including units and the effect of raising concurrency.

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?

Names a specific mechanism and resource: a 'TCP connect port scan' of a host. That is far more precise than a generic 'scan' and tells the agent which scan technique is used. It does not distinguish itself from the closely related siblings pentest_vuln_nmap and pentest_vuln_nmap_preset, which also enumerate ports, so it falls short of a 5.

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 only usage signal is the phrase 'in-scope host', which hints that scope must be validated first (e.g. via pentest_scope_check). There is no statement of when to prefer this over the nmap or nmap_preset siblings, nor any exclusion or prerequisite guidance.

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