read_directory

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

No annotations are provided, so the description must disclose behavioral traits. It only states it lists files and folders but does not address permissions, hidden files, recursion depth, or error handling. This is insufficient for a complete behavioral understanding.

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 with two short sentences. Every word is relevant and necessary, making it efficient for the AI agent to parse.

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?

Without an output schema, the description should indicate what the tool returns (e.g., file names, metadata). It fails to do so. Additionally, it does not address the existence of the similar sibling 'list_directory', leaving the agent potentially confused about which to 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?

The input schema already provides a clear description of the 'path' parameter, including relative and absolute options. The description adds no additional information, so it meets the baseline but does not enhance it.

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 folders in a directory. It uses specific verbs ('List') and resources ('files and folders'), making the purpose unambiguous. While there is a sibling tool 'list_directory' with a similar name, the description adds context about 'accessible roots' which hints at its scope.

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 suggests using the tool to explore file structure within accessible roots. However, it provides no guidance on when not to use it or how it differs from the sibling 'list_directory' tool. This leaves ambiguity for the AI agent.

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