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

With no annotations, the description carries the behavioral burden. It does disclose the key method, 'TCP connect scan', which is a meaningful behavioral detail, but it omits permissions, rate limits, or potential impact of scanning a target.

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 extremely short and front-loads the core action in a scannable colon-separated format. It is concise and avoids padding, though it sacrifices essential input detail.

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 one-parameter tool, the description still fails to define the input and gives no usage context versus sibling tools. An output schema exists, so return values are less critical, but the missing parameter semantics make the description incomplete.

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 never mentions the q parameter or what value it expects. An agent cannot determine whether q is a host, IP address, port list, or something else.

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 specific action and resource: a TCP connect scan over common and camera ports. It is clear and distinguishes itself from generic port lookup tools, though it does not explicitly name a sibling or define what the scan target is.

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 on when to use this tool versus nearby siblings like port, portlookup, or portquick. The mention of camera ports implies a specialized use case, but the description never states exclusions or alternatives.

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