list_notesView Markdown files in a folder as a tree to locate notes on a NAS connection.
List the Markdown files (as a tree) under a folder on a connection.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Folder, default the root | |
| connection | Yes | The connection id (from list_connections) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the result is a tree of Markdown files, but does not mention read-only behavior, pagination, sorting, error cases, or any side effects. Basic but minimal.
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?
One concise sentence with no redundant words. The description is tightly scoped and immediately understandable.
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 no output schema, the description provides enough context (Markdown files, tree structure, folder scope) to understand what will happen. It could mention output format or sorting, but it is not needed for basic usage.
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?
Both parameters are described in the schema with 100% coverage. 'path' is explained as a folder with a default root, and 'connection' references list_connections. The descriptions add useful context beyond just the names.
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 the verb 'List' and the specific resource 'Markdown files' with a scoped location ('under a folder on a connection'). This distinguishes it from sibling tools like read_note, write_note, and search_notes, so the purpose is unmistakable.
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?
Usage is implied but not explicit. The description does not contrast with search_notes (e.g., 'use this to browse, use search_notes to find by content'), so the when-to-use guidance is only inferred from the tool name and sibling context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.