list_files

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the operation is a list, but does not mention read-only nature, pagination, recursion, or limits. This is insufficient for full 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 sentence, very concise, and front-loads the action. However, it lacks structure and does not fully capitalize on its brevity to convey additional useful information; it is just barely complete enough to earn its place.

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?

Despite having an output schema, the description does not explain what is returned (e.g., file names, paths, metadata). With no annotations and a simple but not fully specified tool, the description leaves gaps regarding scope (depth) and inclusion of folders vs. files.

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%, meaning the description must add meaning. It mentions 'folder' and 'ext' filters but does not explain their format (e.g., full path vs. name, with/without dot). Minimal value added beyond the schema's property 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?

The description clearly states the tool lists files in the vault and mentions optional filters, which distinguishes it from sibling tools like 'list_folders' or 'search_vault'. However, it does not specify what qualifies as a file (e.g., all vault files or just markdown), leaving minor ambiguity.

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 general file listing with optional filters, but provides no explicit guidance on when to use this vs. alternatives like 'search_vault' or 'list_folders'. The mention of filters gives some context, but no when-not-to-use or prerequisite information.

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