Import hosts from an OpenSSH config file

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

Annotations already indicate a mutating, non-idempotent operation with no destructive hint. The description adds no further behavioral context beyond restating the import action, leaving important details unstated—especially how existing hosts are handled and what the overwrite parameter actually does.

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 at two sentences, front-loads the core action, and avoids unnecessary detail. There is minor redundancy in repeating 'OpenSSH config file,' but it does not hurt usability.

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 import tool with one required parameter and no output schema, the core call is clear: provide raw config content. However, the behavior of overwrite and the handling of duplicate or existing hosts are omitted, leaving a moderate gap that could cause incorrect agent decisions.

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 describes content as 'Raw text content of the SSH config file,' but overwrite has no schema description. The description repeats the content meaning without adding syntax or format details, and it provides no clarification for the undocumented overwrite parameter, leaving half the parameters under-specified.

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 states a specific action—'Import hosts from an OpenSSH config file'—with a clear resource (hosts) and source format. It does not explicitly distinguish this from sibling tools like termix_hosts_bulk_import_ssh_hosts, but the OpenSSH config source is a meaningful differentiator on its own.

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 intended use case is implied: use this tool when the user has an OpenSSH ~/.ssh/config file and wants to import its hosts. However, there is no explicit guidance about when to prefer alternatives such as termix_hosts_bulk_import_ssh_hosts or termix_hosts_create_ssh_host, nor any mention of exclusions.

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