Four tools with basic schemas and minimal descriptions. All tools have input schemas with required parameters and type definitions, but descriptions are generic (10-30 chars) and lack context for LLM selection. No output schemas documented. Parameters lack format constraints, ranges, or validation guidance. No error handling patterns visible. Tool names follow verb_noun convention but descriptions do not explain WHEN to use each tool or what distinguishes them. Missing idempotency, pagination, and composition guidance.

• Expand tool descriptions to 50-200 chars. Example: 'read_file: Read and return the full contents of a text file. Use this to inspect configuration files, logs, or source code. Returns the file content as a string. Fails if the file does not exist or is not readable.'
• Document output schemas for each tool. Example for read_file: {"type": "object", "properties": {"content": {"type": "string", "description": "Full file contents"}, "size_bytes": {"type": "integer"}}, "required": ["content"]}
• Add format constraints to path parameters. Example: 'path: Absolute or relative file path. Must not contain .. or symlinks. Restricted to /tmp and current working directory for security.'
• Add error handling guidance to descriptions. Example for write_file: 'Overwrites existing files. Returns error if directory does not exist or permissions denied. Errors are not retryable, check path and permissions before retrying.'
• Add idempotency and confirmation pattern to write_file. Example: 'Add a dry_run parameter (boolean, default false). When true, validates the path and returns what would be written without modifying the file. When false, writes and returns success or error.'