list_ports

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

No annotations exist, so description must provide all behavioral context. It covers basic behavior and output format for single/multiple hosts but omits error handling, permissions, or system impact details.

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?

Two sentences efficiently convey the main purpose and additional usage details, front-loading essential information without redundancy.

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?

With no output schema and three parameters, the description explains return types for both modes and optional filtering. It lacks details on default behavior (if no parameters) and error scenarios, but is fairly complete for a list 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 covers all parameters 100%, so baseline is 3. The description adds value by clarifying the semantic difference between 'host' and 'hosts' and the output format, thus scoring above baseline.

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 states it lists active listening TCP/UDP ports, processes, and PIDs. It distinguishes itself from siblings like list_hosts and search_processes by its specific function.

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?

It explains when to use 'host' vs 'hosts' and recommends 'hosts' for scanning multiple machines. It mentions optional port filtering but lacks explicit when-not-to-use guidance.

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