ssh_config_lookup

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

With no annotations, the description carries the burden of behavioral disclosure. The verbs 'Resolve' and 'Shows' strongly imply a read-only operation with no side effects, and it specifies the data source (~/.ssh/config). It does not explicitly state that it avoids network connections or modifications, but the read-only nature is clear enough for an agent to infer safety.

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?

Two concise sentences with no redundancy. The first sentence front-loads the primary function and output details, while the second gives direct usage guidance. Every word contributes to understanding the tool.

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 single-parameter lookup tool, the description covers the key aspects: what it does, what it returns (including the catch-all 'all other options'), and when to use it. No output schema exists, but the description's enumeration of output fields sufficiently informs the agent of expected results.

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 input schema already fully describes the single 'host' parameter as an SSH hostname or IP address (100% coverage). The description adds no additional semantic beyond what the schema provides, so the baseline of 3 is appropriate.

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 precise verb ('Resolve') and a specific resource ('effective SSH configuration for a host'), listing the exact output fields (hostname, user, port, identity files, proxy settings). This clearly differentiates it from sibling tools like ssh_exec (execution) and ssh_read_file (file access), leaving no ambiguity about its function.

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 explicitly states when to use it: 'Use this to understand how SSH will connect to a host.' It provides the context but does not explicitly mention exclusions or alternatives. However, by describing the tool's purpose as configuration resolution, it implicitly steers agents away from execution or file transfer tools.

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