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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the protocol (TCP) and a concrete timeout (2s), which is useful, but it does not mention what the scan does with the supplied input, whether it is a single-port or range scan, or any safety/network side-effect caveats.

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 compact and front-loaded: it states the purpose, protocol, and timeout in a single scannable phrase with no filler. It is not a 5 because the brevity sacrifices essential input semantics, but as a concise teaser it is well structured.

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?

An output schema exists, so return values may not need explanation, but the description still fails to define the input contract or provide selection guidance among close sibling tools. Given no annotations and a completely undocumented 'q' parameter, the description is materially incomplete for reliable 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?

The only parameter, 'q', has 0% schema description coverage, and the tool description never explains what q should contain—port number, hostname, or host:port combination. Since the description does not compensate for the undocumented schema, an agent cannot reliably know how to populate the input.

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 names a concrete action: a TCP port scan with a 2-second timeout, so an agent can infer it probes reachability of a TCP port. It does not explicitly distinguish it from siblings like 'portscan', 'portlookup', or 'port', which costs the fifth point.

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 guidance about when to use portquick versus the many related sibling tools such as port, portlookup, or portscan. The words 'quick' and '2s timeout' imply a lightweight check, but no alternatives or exclusions are stated.

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