Port Scan

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

No annotations are provided, so the description carries the full burden. It says nothing about whether the scan is intrusive, what protocol(s) it uses (TCP connect, SYN, UDP), whether it may be slow or rate-limited, or whether it triggers IDS/logging. Only the schema name hints at any 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?

It is a single short sentence with no waste, but it is under-specified rather than efficient. Nothing is front-loaded that helps selection or invocation.

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 network-scanning tool with no annotations and no output schema, the description should state protocol, intrusive-ness, and result shape. It omits all of that, and does not help the agent distinguish it from the several overlapping network-test siblings.

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%, documenting target, ports range format, and timeout default, so the baseline applies. The description adds no additional semantic detail such as port syntax beyond ranges, hostname vs IP handling, or timeout behavior.

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?

States a verb (scan) and resource (ports on a target), which is minimally specific. It does not distinguish this from siblings like nmap_scan, service_discovery, or netcat_test, so an agent cannot tell which scanning tool to pick from the name and description alone.

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 indication of when to use this versus nmap_scan or service_discovery, no prerequisites, no note about when a simple connect scan is the right choice. Usage is only implied by the tool name.

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