check_connectivity

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

With no annotations provided, the description carries the full burden. It helpfully discloses that private/loopback hosts are blocked, which is real behavioral context, but it does not describe the return format (e.g., boolean reachability vs. latency), error behavior on timeout, or rate limits. Partial disclosure only.

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?

Front-loaded one-line purpose followed by a compact Args block. Efficient, though the adjacency of the blocking constraint inside the host arg is slightly awkward. No filler.

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, non-destructive TCP probe with no output schema, no annotations, and no auth requirements, the description is nearly complete. Only the return/error behavior is unspecified, which is a minor gap given the low complexity.

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%, so the description must compensate. It documents all three parameters including bounds for port (1-65535), the timeout unit (seconds), and the input type for host (hostname or IP), plus the blocking constraint. Good compensation, though the default timeout is carried by the schema, not the description.

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?

States a specific verb (check), resource (TCP port connectivity), and scope (public host). Clearly distinguished from siblings like resolve_dns, fetch_url, or get_service_status, which describe name resolution, HTTP fetching, and local service status respectively.

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 says what it tests and that private/loopback hosts are blocked, which implies when it is applicable, but it never states when to prefer this over siblings like fetch_url or get_service_status, nor describes supported use cases. Usage is implied rather than explicit.

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