Mne List Files

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

No annotations are present, so the description carries the behavioral disclosure burden. It communicates the default directory fallback and optional glob, but it does not mention recursive vs. non-recursive listing, sorting, hidden files, or failure behavior. The core behavior is clear for a simple read-only listing tool.

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?

Two concise sentences with no filler. The main action, supported file types, default directory, and optional glob are all front-loaded and easy to scan.

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 an output schema, low complexity, and only two optional parameters, the description covers file types, default paths, and pattern usage well. Minor gaps around recursion and path semantics exist but do not prevent correct invocation.

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%, but the description adds meaning by associating 'directory' with the default location and 'pattern' with a glob pattern. However, it does not explain glob syntax, path resolution, or how directory and pattern interact, so the compensation is partial.

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?

Uses a specific verb ('List') and names the exact resource: neurophysiology data files with supported extensions under a directory. It is clearly distinct from sibling processing/plotting tools because it is the only file-listing helper in the set.

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?

Provides actionable guidance by stating the default directory behavior and the optional glob pattern. It does not explicitly name alternatives or exclusions, but there are no sibling listing tools, so the context is sufficient for an agent to know when to invoke it.

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