디렉토리 목록

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

No annotations are provided, so the description carries full burden. It adds a useful behavioral detail by excluding dotfiles, but it does not disclose whether the operation is read-only, the output format, sorting order, or error behavior. This is a basic disclosure, not a comprehensive one.

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 two short sentences; the first states the core functionality, the second adds the meaningful dotfile exclusion. Every word earns its place with no redundancy or fluff.

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 two-parameter list tool with no annotations or output schema, the description is adequate but incomplete. It omits the return value shape, potential errors, and whether any side effects occur, leaving gaps for an AI agent to infer.

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?

Schema description coverage is 100% for both parameters (path and recursive), so the description adds no additional parameter-level meaning. Baseline of 3 is applied because the schema already documents the parameters well.

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 states exactly what the tool does: 'Returns file/folder list in Vault directory' with a specific verb and resource. This clearly distinguishes it from sibling tools like create_directory or read_note.

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 usage for listing directory contents via the Vault-relative path and recursive flags, but it does not explicitly state when to prefer this over alternatives or when not to use it. The context is clear, but exclusions and alternatives are missing.

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