net.portscan

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this is a bounded TCP connect scan, defaults to top common ports, and caps scanning at 256 ports, but it omits permissions, intrusive side effects, timing, rate limits, and return behavior.

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 front-loaded sentence with little wasted wording. It is perhaps too terse for the tool's risk profile, but the conciseness itself is effective.

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 no annotations, no output schema, and 0% parameter description coverage, the description is not complete enough. An agent would still lack return-value expectations, permission/security context, and clear operational boundaries for a network scanning tool.

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 for both parameters. It partially explains the ports behavior via default top common ports and a 256 cap, though the cap duplicates the schema's maxItems, and it leaves the required host parameter and port-list format essentially undocumented.

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 a TCP connect port scan and scopes it with default common ports and a 256-port cap. It is specific about the resource and method, but it does not distinguish this tool from nearby siblings such as net.portcheck or net.deepscan.

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?

There is no explicit guidance on when to use this tool versus net.portcheck, net.deepscan, or other network tools. The description implies a port-scanning use case but gives no exclusions, prerequisites, or alternative-routing advice.

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