list_directory

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'list' implies a read-only operation, and 'all files and folders' conveys the scope. However, it does not disclose edge cases (e.g., hidden files, recursion, or error handling), which is a notable gap for unannotated tools.

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, front-loaded sentence that directly states the tool's action and target. No unnecessary words or information, achieving maximum conciseness.

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 one-parameter tool with an output schema, the description is functional but minimal. It does not clarify whether listing is recursive, how directories vs. files are represented, or any behavior beyond the basic 'list all'. Given the presence of an output schema, return values are covered, but other contextual details remain vague.

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 0% description coverage, so the description must compensate. It introduces 'given directory path', clarifying that the 'path' parameter should point to a directory. However, it adds no format details (absolute vs relative, supported types), and the single parameter's name is already fairly self-explanatory.

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 uses a specific verb ('List') and resource ('all files and folders in the given directory path'), clearly distinguishing this directory-listing tool from sibling file operations like read_file or delete_file.

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: use this when you need to list directory contents. However, it does not explicitly mention when not to use it or provide alternatives. Sibling tools operate on files, so context is present but not spelled out.

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