list_directories

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

No annotations are provided, so the description carries full burden. It states the basic operation but omits behavioral details such as whether hidden folders are included, symlink handling, performance implications, or how respect_gitignore affects output.

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, using a single sentence plus an emphatic instruction. Every word serves a purpose, and the key distinction (folders only) is front-loaded.

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 complexity of three parameters, no output schema, and no annotations, the description is insufficient. It does not explain the output format (e.g., tree structure as text or object), depth behavior, or gitignore functionality, leaving significant gaps for correct tool invocation.

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?

Schema description coverage is 0%, meaning no parameter descriptions. The tool description adds no information about the three parameters (directory, max_depth, respect_gitignore), leaving the agent to infer meaning solely from names and types.

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 explicitly states 'List directory tree structure (folders only, no files)' with a specific verb and resource, clearly distinguishing from sibling tools like scan_directory which likely include files. The instruction 'USE THIS to see folder hierarchy' reinforces its unique purpose.

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 provides a clear context ('USE THIS to see folder hierarchy') but lacks explicit guidance on when not to use it or alternatives among the eight sibling tools.

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