list_notes

Does 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 tool only returns markdown note paths, scopes to a folder if supplied, omits the folder scope when empty, and returns newline-separated paths relative to vault root. This is reasonably transparent for a read-only listing operation, though it does not mention edge cases like invalid folders or recursive traversal.

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 compact and well-structured, with a one-sentence summary followed by clear Args and Returns sections. Every sentence adds necessary information, and the main purpose 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?

For a simple list tool with one optional parameter and no annotations, the description covers purpose, parameter semantics, scoping behavior, and return format. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 provides no description for the 'folder' parameter, but the description fully compensates: it defines the parameter as a subfolder relative to vault root, explains the empty case, and clarifies the output semantics. This gives the agent everything needed to understand and supply the parameter correctly.

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 specific action ('List all markdown notes in the vault') and the optional scope ('scoped to a folder'). This distinguishes it from sibling tools like list_folders (folders, not notes) and search_notes (content search, not listing).

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 gives clear context for when the tool is useful: listing all notes or notes within a specific subfolder. It does not explicitly name alternatives or exclusions, but the behavior is straightforward enough that an agent can infer appropriate usage.

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