list_directoryLists direct children of a folder, providing its subfolders and note IDs. Use it to see what's inside a directory in a markdown vault.
Direct children of a folder: subfolders and note ids.
| Name | Required | Description | Default |
|---|---|---|---|
| prefix | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavior disclosure. It usefully states that only direct children are returned and that the result consists of subfolders and note ids, signaling non-recursive behavior and a lightweight output format. It does not mention ordering, hidden entries, or edge cases, but the key behavioral scope is clear.
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 that immediately states the core behavior with no filler or redundancy. It is well-suited for quick agent scanning.
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 listing tool with an output schema, the core operation is adequately described. The main gap is the meaning and usage of the 'prefix' parameter, which is essential for targeting a specific folder, and no alternative tools are referenced. This makes the definition adequate but not fully complete.
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 one parameter, 'prefix', with no description and 0% schema description coverage. The tool description never mentions 'prefix', so its meaning, format, and effect on the folder being listed are left entirely to inference. The name and default '' give only a weak clue.
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 resource (a folder) and the scope of results ('Direct children', 'subfolders and note ids'), which distinguishes it from list_notes or search_notes by focusing on a shallow directory listing. It lacks an explicit verb, but the title 'List Directory' supplies the action.
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 phrase 'Direct children of a folder' implies when to use this tool: when you need a shallow listing of a folder rather than full note content. However, it does not name any sibling tool or provide explicit when-not-to-use guidance, so the usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.