This is a demo client, not an MCP server. The code shows a StdioClientTransport connecting to @modelcontextprotocol/server-filesystem (an external server), not defining tools itself. Tool definitions (list_directory, read_file) are inferred from the external server being invoked, not visible in this repo's source. Additionally, descriptions are minimal (10-20 chars), parameter descriptions are present but generic, and no output schemas are documented in this codebase. The repo provides no tool definitions, error handling, or validation logic, it is purely a client demo.

• If this is intended as a server, define tools directly in this repo with full schemas, descriptions (50-200 chars), and output documentation. Do not rely on external server delegation.
• Expand tool descriptions to 50-200 characters, explaining WHAT the tool does, WHEN to use it, and what it returns. E.g., 'List all files and directories in a given path. Returns file names, types, and sizes. Use to explore directory structure before reading files.'
• Document output schemas for both tools. E.g., list_directory returns {items: [{name: string, type: 'file'|'directory', size: number}], total: number}.
• Add error handling guidance: 'If path does not exist, returns error with available parent directories. If permission denied, returns error with required permissions.'
• Add parameter constraints: 'path must be a valid absolute or relative path; relative paths are resolved from the server's working directory.'