List files in any directory within the secure sandbox by specifying a path, or rely on the current directory default to quickly inspect available files.
List files in a directory in the sandbox
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Directory path to list (default: current directory) | . |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states the core listing action and does not mention whether results include directories, hidden files, sorting, or error behavior.
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?
One concise sentence with no filler; the action and sandbox scope are front-loaded. Every word earns its place.
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 one-parameter listing tool, the description covers the essential operation. However, without an output schema or annotations, it leaves unstated what the returned listing contains (e.g., names only, directories included, hidden files).
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 single parameter path is already fully described in the schema (directory path with default '.'). The description adds no new parameter meaning, so the high schema coverage establishes a baseline of 3.
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?
States a clear, specific action: list files in a directory within the sandbox. This distinguishes it from read_files (file content) and write_files/remove_files (mutations).
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 it should be used when an agent needs to see what files exist in a path within the sandbox. However, it does not explicitly contrast it with alternatives like read_files or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.