This is a STDIO-only example server with 8 basic tools. All tools have descriptions (10-50 chars, below the 50-200 char LLM-optimized baseline) and input schemas with typed parameters. However, descriptions are minimal and lack context for LLM selection. No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). The write_file tool is marked WRITE but has no confirmation or dry-run pattern. Tool names are clear (add, subtract, multiply, divide, read_file, write_file, list_directory, get_weather) but descriptions do not explain WHEN to use each tool or what happens on error. Parameters lack format constraints (e.g., get_weather 'location' accepts any string; no validation hints). No pagination for list_directory despite potential for large results.

• Expand tool descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it, and any prerequisites. E.g., 'Adds two numbers and returns the sum. Use for arithmetic operations in multi-step calculations. Returns a single numeric result.'
• Document output schemas for all tools. Specify field names, types, and ranges. E.g., get_weather returns {temp: number, humidity: number, condition: string, location: string}.
• Add tool annotations: mark read_file, list_directory, get_weather with readOnlyHint=true; mark write_file with destructiveHint=true; mark add/subtract/multiply/divide with idempotentHint=true.
• Implement confirmation pattern for write_file: add a 'dry_run' parameter or require explicit 'confirm=true' to prevent accidental overwrites.
• Add pagination to list_directory: accept 'limit' (default 50, max 500) and 'offset' parameters; return {entries: [...], total: number, has_more: boolean}.