ssh_list_dir

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 only states the basic action; it fails to disclose behaviors such as how connections are handled, whether hidden files are excluded by default, output format, or error handling. This is a minimal disclosure with no additional behavioral context.

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, clear sentence with no redundant wording. It is front-loaded and immediately conveys the tool's purpose. However, it is very brief, but that is more a completeness issue than a conciseness issue.

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?

With no output schema and no annotations, the description should explain what the tool returns and any relevant behaviors. It only says it lists files and subdirectories, ignoring defaults like remote_path='~' and show_hidden=false, timeout handling, and return format. The tool has 4 parameters, making this description inadequate for reliable agent use.

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 0%, and the description does not compensate. None of the four parameters (host, timeout, remote_path, show_hidden) are explained beyond their names. The description only implies remote_path via 'specified directory', leaving host, timeout, and show_hidden undefined.

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 lists files and subdirectories in a specified remote directory. This distinguishes it from sibling tools like ssh_exec, ssh_upload, and ssh_download, 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?

The description provides no guidance on when to use this tool versus alternatives such as ssh_exec (which could run ls) or ssh_stat_file. There are no usage scenarios, prerequisites, or exclusions mentioned.

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