nc_banner_grab

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

With no annotations, the description carries the full burden. It discloses that it sends a newline or custom data and waits for a response, which is a key behavioral trait. However, it doesn't mention error handling or what happens if no response is received, a minor gap.

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 concise and well-structured: it opens with the primary purpose, explains the mechanism in one sentence, and then lists parameter definitions. Every sentence earns its place with no 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?

The tool is fairly simple, and the description covers its purpose and parameters well. However, with no output schema, it does not state what the return value looks like (e.g., the banner text or an error on timeout). This is a notable gap for a network 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 description coverage is 0%, but the description explicitly explains each parameter: host, port, timeout, and send_data, including escape sequences. This adds significant meaning beyond the bare schema, fully compensating for the lack of schema descriptions.

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 the tool grabs a service banner from host:port, using a raw async socket. This is a specific verb+resource and distinguishes it from sibling tools like nc_port_check, which only checks port availability.

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?

The description clearly implies its use for banner grabbing after a port is known to be open, but does not explicitly mention alternatives or when not to use it. The context is clear, though no exclusions are stated.

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