netcat

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

With no annotations provided, the description carries the full burden. It does disclose the core behaviors (connect, listen, transfer files, spawn shells) and the connect/listen modes via parameters, but it does not mention potential security implications, privilege requirements, or that it is a raw socket utility that may be flagged by firewalls. For a tool with security-sensitive capabilities, a bit more disclosure would be ideal, but the basics are covered.

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 with no wasted words. The core purpose and use cases are front-loaded, and the alternative tool guidance is neatly appended. Perfectly concise and 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?

For a simple utility with full schema coverage and no output schema, the description adequately covers main use cases, modes, and alternatives. It could mention that UDP is supported (though the description says TCP/UDP) or touch on interactive usage, but these are minor. Overall, an agent can correctly invoke it for common tasks without further information.

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% for all three parameters (host, port, connect), including the default behavior of connect=true. The description adds minimal extra meaning beyond the schema, only implicitly referencing listen vs. connect. This meets the baseline for full schema coverage but does not elevate it.

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 is a TCP/UDP connection utility for connecting, listening, file transfer, and shell spawning. It specifies concrete use cases like service banner grabs and connectivity tests, and explicitly contrasts with nmap for enumeration and tcpdump for packet analysis, making it easy to distinguish from siblings.

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 provides explicit when-to-use guidance (quick banner grabs, port tests, shells) and names alternatives with conditions ('prefer nmap' for structured enumeration, 'tcpdump/tshark' for raw analysis). This is exactly the kind of routing an agent needs.

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