List allowed SSH Host aliases

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds valuable behavioral detail: returns only safe connection metadata, never exposes private keys/IdentityFile paths/agent sockets/ProxyCommand, and re-parses config without restarting. This is consistent with the annotations.

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 front-loaded with the main purpose, then adds safety guarantees, reload guidance, and a pointer to ssh_open. Every sentence earns its place; there is no redundancy or 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?

Since there is no output schema, the description adequately explains return values (alias, hostname, user, port, proxy_jump) and exclusions. It also covers parameter behavior. For a simple list tool, this is 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?

Schema has 0% description coverage, so the description must compensate. It fully explains the reload parameter: passing reload=true after editing ~/.ssh/config re-parses without restarting the MCP server. This adds clear meaning beyond the boolean type and default.

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 lists allowed OpenSSH Host aliases from local ssh_config and an explicit allowlist, with a specific resource and scope. However, with a sibling named ssh_list that could also be a listing tool, there is no explicit differentiation from that sibling, preventing a 5.

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 gives clear usage context: use this to discover aliases for ssh_open, and pass reload=true after editing ~/.ssh/config. It does not explicitly state when not to use it or name alternatives among the sibling tools, so it falls short of a 5.

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