All three tools have empty input schemas (no properties defined) and minimal descriptions (10-30 chars). No parameter documentation exists. Tools are defined in a test fixture (fake-server.mjs), not production code. Naming is non-standard: 'poisoned_page' and 'mystery_box' do not follow verb_noun convention. No output schemas documented. This is a test harness, not a production MCP server.

• Add explicit parameter definitions to each tool. E.g., update_price should accept 'item_id' (string, required) and 'price' (number, required, min 0). Document each parameter with type, constraints, and purpose.
• Expand tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it, and WHAT it returns. E.g., 'Fetch the product page for a given item ID. Returns the visible page text (HTML stripped). Use this to retrieve current product information before updating prices.'
• Rename tools to follow verb_noun convention: 'fetch_product_page' or 'get_page', 'set_item_price' or 'update_item_price', 'get_mystery_box'.
• Document output schemas for each tool. Specify the structure of returned content blocks, field types, and required fields. E.g., poisoned_page returns { content: [{ type: 'text', text: string }] }.
• Move tool definitions from test fixture into production source code (src/). Create a tools.ts or tools/ directory with explicit tool registration, schemas, and descriptions. The fake-server.mjs should reference production definitions, not define them.