file.list

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

No annotations are provided, so description carries full burden. It states 'List files/directories' but does not disclose traits like read-only nature, sorting order, pagination behavior, or the effect of missing parameters. The description adds little beyond the schema.

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?

Single sentence that is front-loaded with the primary action. No redundant words or information. Very compact and efficient.

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 complexity (6 parameters, no output schema, no annotations), the description is insufficient. It does not explain the return format, pagination using limit/offset, the necessity of vault parameter, or how glob matching works relative to directory. Users are left guessing important details.

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 has 6 parameters with only 33% description coverage (glob and directory have descriptions). The description mentions 'glob filter' and 'recursively' but these are already evident from the schema. It does not clarify the meaning of limit, offset, vault, or how they interact.

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?

Description clearly states verb 'List' and resource 'files/directories in the vault'. It mentions optional recursion and glob filter, which clarifies scope. However, it does not explicitly distinguish from sibling tools like vault.list or search.content, but their purposes are different enough.

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 vs alternatives. The phrase 'optionally recursively' hints at usage but lacks context like 'use file.find for content search' or 'vault.list for vault properties'. No exclusions or prerequisites provided.

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