list_directory

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It's a read-only list operation which is intuitively safe, but the description doesn't explicitly state that it performs no mutations, how it handles empty folders, or what happens when the path is invalid or outside the allowed root.

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 concise sentence with no wasted words. It front-loads the purpose clearly. However, it's arguably under-specified enough that brevity borders on lacking necessary context rather than being efficiently complete.

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 list/read tool operating within permissions constraints, the description is thin. There's no output schema, no annotation coverage, and the single parameter lacks detail. The key ambiguity around 'allowed folder' and path resolution behavior is never addressed, which matters for an agent deciding how to interact with a filesystem.

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 schema has 1 parameter with 0% description coverage and no enums. The path parameter is self-explanatory given the tool name, but the description doesn't clarify path format expectations (absolute vs relative), whether the allowed folder is the base, or what errors occur for disallowed or nonexistent paths.

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 clear action ('List files and folders') applied to a resource ('an allowed folder'), which is reasonably specific. However, it doesn't distinguish this from sibling tools like read_file or find-style operations, and 'allowed folder' is vague about what defines 'allowed'.

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?

No guidance is provided on when to use this tool versus alternatives. The mention of 'allowed folder' hints at a permission restriction but doesn't explain what makes a folder 'allowed' or when the agent should choose this over create_directory or other navigation tools.

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