port_owner

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

No annotations are present, and the description gives no behavioral details such as whether the tool queries a remote host, requires specific permissions, or has side effects. The agent has no insight into safety or operation.

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 but at the cost of being uninformative. Conciseness should not sacrifice necessary detail; here it is under-specified rather than efficiently clear.

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?

Despite having an output schema, the description provides no context about the tool's I/O behavior. For a simple tool, something as basic as 'Given a port, returns the owning process or user' is missing. It is completely 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?

The input schema has two parameters with zero description coverage. The description adds no meaning about what 'host' and 'port' represent or how they are used. The agent must guess their semantics.

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 is merely a label 'Kali Agent MCP tool: port_owner' which restates the name without specifying a verb or clarifying what 'port_owner' actually does. It fails to distinguish from similar siblings like 'port_list'.

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 usage context is provided. There is no indication of when to use this tool or when to avoid it, and no alternatives (e.g., 'port_list') are mentioned.

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