Server Test Connection

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

With no annotations, the description carries the full burden, and it does disclose that the tool probes both SSH reachability and Slurm command availability, implying a read-only, non-mutating diagnostic. However, it says nothing about timeouts, failure behavior, or whether credentials/config are required, which matters for a connectivity test.

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?

A single front-loaded sentence with zero filler that covers both checks. Nothing is redundant or padded.

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 one-parameter diagnostic with no output schema and no annotations, the description is only minimally sufficient. It omits what the check returns (e.g., which component failed) and how the caller should react to a failure, which an agent must know without a return schema.

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% and the single parameter 'server_alias' (default 'default') is never mentioned in the description. The phrase 'configured SSH connectivity' hints at named configured servers but does not explain what a server alias is or how the default resolves.

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') and two concrete resources ('SSH connectivity', 'Slurm command availability'), which tells an agent this is a diagnostic rather than an execution tool. It does not explicitly name alternatives such as ssh_execute or slurm_submit, so sibling differentiation is left implicit.

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?

There is no statement of when to call this versus the many sibling tools (ssh_execute, slurm_submit, server_list). The diagnostic intent is inferable from the verb 'Check', but no context or exclusions are provided.

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