port_check

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

Since no annotations are provided, the description fully bears the burden of behavioral disclosure. It explains that the tool performs a TCP connection check, optionally grabs a banner, and returns status, response time, and banner. It also specifies default values for timeout and grab_banner.

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 well-structured with a clear purpose statement, usage suggestions, parameter list, and return info. Every sentence adds value, and it is appropriately front-loaded.

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?

Given the tool's low complexity, the description covers all necessary context: purpose, parameters, and return values. No output schema exists, but the description clearly states what is returned.

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 coverage is 0%, and the description provides detailed parameter semantics via an 'Args' section, explaining each parameter's purpose, type, range, and defaults. This adds significant meaning beyond the schema's type-only definitions.

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 'Check if a TCP port is open and optionally grab service banner', providing a specific verb and resource. It distinguishes itself from sibling tools like batch_port_check by focusing on a single port check.

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 outlines clear use cases: 'verify if a service is listening on a port, check firewall rules, or identify what service is running on a port.' It does not explicitly mention when not to use it or name alternatives like batch_port_check, but the context is sufficient.

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