List Folders

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the core function but does not specify whether subfolders are included recursively, what format the results take, or any permissions/requirements. The optional parent scoping is disclosed, but key behavioral details remain ambiguous.

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 front-loads the main purpose and mentions the optional scope without unnecessary words. Every word earns its place.

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 tool with one parameter, the description covers the basic selection context, but lacks an explanation of the output format and recursive behavior, especially since no output schema is provided to fill that gap.

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 already describes the parent parameter as 'Parent folder path, or empty for root' with 100% coverage, so the description adds only slight reinforcement by mentioning vault-wide vs specific directory listing. It does not provide materially new parameter meaning.

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 'List all folders in the Obsidian vault or within a specific directory' with a specific verb (List) and resource (folders), and distinguishes this from sibling tools like list_notes by focusing on folders rather than notes or other actions.

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 when to use the tool (when listing folders is needed) and clarifies the optional directory scope, but it does not explicitly mention alternatives or when not to use it, such as comparing with get_vault_overview or search_by_tag.

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