list_directory

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states the basic action (listing directory contents) and default behavior (current working directory), it doesn't describe important behavioral traits such as: what format the output takes (e.g., list of filenames, detailed metadata), whether it includes hidden files, error handling for invalid paths, permissions required, or any rate limits. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 extremely concise (one sentence) and front-loaded with the core purpose. Every word earns its place: 'List contents of a directory on the VPS' establishes the primary action, and 'Defaults to current working directory' adds crucial behavioral context. There's no wasted verbiage or redundancy.

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?

Given the tool's moderate complexity (directory listing operation), lack of annotations, and absence of an output schema, the description is incomplete. It doesn't explain what the tool returns (file list format, metadata included), error conditions, permissions needed, or how it interacts with sibling tools like 'change_directory'. For a tool with no structured output documentation, the description should provide more complete context about the operation's results and constraints.

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 description mentions the default behavior ('Defaults to current working directory') which adds context beyond the schema's description of the 'path' parameter ('Path to list (relative to CWD or absolute)'). However, with 100% schema description coverage (the single parameter is fully documented in the schema), the description doesn't need to compensate heavily. It provides some additional semantic context about defaults, but doesn't explain parameter interactions or constraints beyond what's in the schema.

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 verb ('List') and resource ('contents of a directory on the VPS'), making the purpose immediately understandable. It distinguishes from siblings like 'get_current_directory' (which returns only the current path) and 'read_file' (which reads file contents rather than listing directory contents). However, it doesn't explicitly mention what specific information is returned (e.g., files vs. directories, permissions, sizes).

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 usage context by stating 'Defaults to current working directory,' suggesting this tool should be used when you want to see directory contents, with an optional path parameter. However, it doesn't explicitly state when to use this versus alternatives like 'get_current_directory' (which only returns the current path without listing) or 'execute_command' (which could run custom listing commands). No explicit when-not-to-use guidance or prerequisite information is provided.

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