list_vault_files

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

Annotations are absent, so the description must fully disclose behavior. It states it lists markdown files but omits details such as whether directories are recursed, whether hidden files are included, pagination behavior, or the format of the returned file identifiers. This lack of context reduces transparency.

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 a single, concise sentence that is front-loaded with the core action. However, it sacrifices necessary detail for brevity, making it less useful than a slightly longer but more informative description.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description is insufficient. It does not explain return values, pagination, recursion behavior, or how it compares to the many sibling tools (e.g., get_files_by_tag, search_vault_simple). The tool is moderately complex, requiring more context.

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 0%, so the description must clarify parameters. It only mentions 'optionally under a subdirectory' for the directory parameter, with no details on format or default. The limit parameter is not addressed at all, leaving its purpose and constraints ambiguous.

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 verb 'List' and the resource 'markdown (.md) files in the vault', with an optional subdirectory qualifier. This distinguishes it from sibling tools like get_vault_file (retrieves a single file) and get_recent_files (lists recently modified files).

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?

No explicit guidance on when to use this tool versus alternatives. While the description mentions optional subdirectory filtering, it does not compare to related tools like search_vault_simple or get_files_by_tag, nor does it specify when listing files is appropriate.

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