list_folders

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

Implies a simple read-only operation, but does not disclose whether it returns folder names or full paths, whether subfolders are included recursively, or if there are any limitations on the number of folders listed. With no annotations, more detail would be beneficial.

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?

A single, concise sentence that is front-loaded with the essential action and scope. No unnecessary words.

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 parameterless tool, the description adequately defines the action, but lacks details about output format (e.g., folder paths vs names) and whether the listing is flat or recursive. Still, it covers the core purpose.

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?

No parameters exist, so the description has no parameters to document. Baseline 4 is appropriate as it does not need to add parameter details.

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?

Clearly states verb 'lists' and resource 'folders' within the active Obsidian vault, distinguishing it from sibling tools like list_notes, list_tags, and list_vaults.

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?

Provides no guidance on when to use this tool vs alternatives, such as whether to use list_folders before listing notes in a specific folder, or how it differs from list_vaults.

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