Resolve SSH Host

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context that it reads from ~/.ssh/config, which is consistent and slightly enriches the behavioral model. No contradictions or missing critical behaviors.

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 a single sentence of 10 words with no superfluous information. It is front-loaded with the action and resource, making it easy for an agent to quickly understand the tool's core function.

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 existence of an output schema (not shown here), the description does not need to detail return values. It fully covers the tool's purpose and input requirements, and the annotations cover safety. No gaps are apparent for this simple resolver operation.

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 coverage is 100% with a clear description for the single parameter 'hostAlias'. The tool description does not add extra meaning beyond the schema, but baseline is adequate since schema handles semantics well.

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 uses a specific verb ('resolves') and clearly identifies the resource ('host alias from ~/.ssh/config') and output ('connection parameters'). It distinguishes itself from sibling tools like ssh_hosts_inspect or ssh_list_configured_hosts by focusing on resolution of a single alias.

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 provides no guidance on when to use this tool versus alternatives (e.g., ssh_host_inspect, ssh_list_configured_hosts). It does not mention prerequisites, typical use cases, or exclusions. An agent would have to infer context from the name alone.

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