ssh_list_dir

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

Annotations already indicate readOnlyHint and openWorldHint, so the safety profile is covered. The description adds value by explaining that SSH credentials are private server-side configuration and that the operation returns at most 10000 entries, which is beyond 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?

Two concise sentences, with the core action and limit front-loaded, followed by credential handling and routing to an alternative. No fluff or repetition of schema details.

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 listing tool with annotations covering read-only and open-world behavior, the description covers the action, return limit, credential handling, and when to use the alternative. No critical information for correct invocation is missing.

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 description coverage is 50% (only 'server' has a description, which is already present in the schema). The tool description does not add extra detail about the 'path' parameter beyond implying it is the directory to list. Since coverage is moderate, the description does not compensate further, but the parameters are self-explanatory given the tool's purpose.

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 verb (List) and resource (remote directory) via SFTP on a selected server, and includes a return limit. This clearly distinguishes it from siblings like ssh_stat, ssh_read_file, and ssh_exec, which perform different operations.

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?

It explicitly instructs to use ssh_list_servers when the user has not supplied an exact alias, providing a clear alternative. It also adds a behavioral constraint ('Never ask the user for a password'), which is important for invocation.

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