obsidian_list

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

No annotations are provided, so the description carries the burden of disclosing behavior. 'List' implies a non-mutating read operation, which is transparent enough at a basic level, but it does not specify what the returned list contains (e.g., paths, titles), whether subdirectories are recursive, or how output is structured.

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 one concise, front-loaded sentence with no redundant phrasing. It efficiently communicates both the default behavior and the optional subdirectory behavior.

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?

The tool is simple, with one optional parameter and no output schema. The description is adequate for basic invocation, but it omits return-format details and recursion behavior, which an agent might need to confidently use the result.

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 provides complete coverage of the single 'dir' parameter, including its default and meaning. The description does not add extra parameter guidance, but with 100% schema coverage this is acceptable and meets the baseline.

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 action ('List') and the resource ('all notes in the vault or a specific subdirectory'). It is specific enough to distinguish from read, search, and write operations, though it does not explicitly name sibling tools.

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 communicates a clear use case: enumerate notes in the vault or a chosen subdirectory. It does not explicitly discuss when to prefer search, find, or query, but the context is sufficiently clear for a list/inventory operation.

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