List SSH Hosts

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

No annotations are provided, so the description carries the full burden. It discloses that it reads from local ssh_config and optionally returns cached extended fields, implying a read-only nature. However, it does not explain what 'cached' means, potential staleness, or any side effects. For a simple list operation, this is adequate but not rich.

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 front-load the primary purpose and add an optional behavior. No wasted words, perfectly sized for the tool's simplicity.

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 0-parameter, no-output-schema, no-annotation tool, the description is mostly complete. It clearly states what it lists and the optional cached fields. The only gap is not explaining what 'cached extended fields' entails, but the core functionality is fully covered.

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 has zero parameters, so there are no parameter semantics to explain. The baseline of 4 is appropriate; the description adds no parameter info but none is needed.

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's function: 'List configured SSH hosts from local ssh_config.' It specifies the verb (List), the resource (SSH hosts), and the source (local ssh_config), distinguishing it from sibling tools like exec, upload, and download. The optional 'cached extended fields' adds specific nuance.

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 implies when to use this tool: to enumerate SSH hosts from the local ssh_config file. The context is clear enough given the sibling tools are all execution/transfer operations. However, it does not explicitly mention alternatives or exclusions, such as using 'info' for system information, but the purpose is distinct.

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