PriceMCP has 8 tools with basic schemas and descriptions, but significant gaps prevent higher scores. Tool names follow verb_noun convention (search_price, get_price, list_catalog). Descriptions exist but are brief (avg ~80 chars, below the 194-char baseline). Input schemas are present with type definitions, but parameter descriptions are sparse or missing. Output schemas are undocumented. Error handling is minimal. No tool annotations (readOnlyHint/destructiveHint). The record_decision tool (WRITE risk) lacks confirmation/dry-run pattern.

• Consolidate tool definitions into src/server.ts with explicit MCP tool registration. Verify all 8 tools are registered via createMcpServer() with full schemas and descriptions visible in source.
• Document output schemas for all tools. E.g., search_price returns {subject, offers: [{provider, price, freshness, source}], ranking}. Include field types and required fields.
• Add parameter descriptions for all inputs. E.g., 'category' → 'Optional product category filter (e.g., electronics, home, sports). If omitted, returns all categories.' Range constraints for numeric params (days: 1-365, max_age_hours: 0-8760).
• Implement confirmation/dry-run for record_decision. Return a preview of the decision before committing, or add a 'dry_run' boolean parameter to preview without side effects.
• Add tool annotations: readOnlyHint=true for search_price, list_catalog, search_products, get_price, compare_prices, find_best_offer, get_price_history; destructiveHint=true for record_decision.