check_network_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 states that the tool performs a ping/reach test and returns ping results and DNS resolution status, which implies a read-only diagnostic operation. However, it does not explicitly state safety (no system modifications), required credentials, or rate-limit considerations. The return value description is helpful but not exhaustive.

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 compact and well-structured: a one-sentence purpose, followed by an Args section that documents both parameters, and a Returns section. No fluff or redundant content.

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 simplicity (2 optional params), the description covers the essentials, but it leaves ambiguity around when to use this tool versus siblings (e.g., test_connection), and the lack of annotations means the agent doesn't know if the operation is side-effect-free. A bit more context about typical use cases would make it complete.

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?

The schema only provides type and default for each parameter (0% coverage), so the description must compensate. It does: 'target' is explained as 'IP or hostname to ping/reach', with default shown; 'host_name' is explained as 'Named host from SSH_HOSTS config'. This adds functional meaning beyond the bare schema.

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 opens with a clear, specific action: 'Test outbound network connectivity from the remote server.' This distinguishes it from sibling tools like get_network_info (likely about local network config) and test_connection (likely about SSH connectivity). The scope is explicit (outbound, remote server).

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 does not explicitly reference alternatives or state when-not-to-use. It implies usage context via 'from the remote server' but leaves the agent to infer that it is for outbound reachability checks. No exclusion guidance is present.

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