SteamTools MCP has 2 tools with basic schemas and minimal descriptions. Tool names follow verb_noun convention (get_, search_), which is good. However, descriptions are extremely terse (under 50 characters each), parameter descriptions lack depth, and output schemas are completely undocumented. Error handling returns structured objects but provides no guidance on recovery actions. Input schemas exist and have type definitions, preventing a complete failure, but lack the detail needed for production use. Parameter 'max_results' has a default (10) which is good, but lacks min/max bounds documentation. The caching and rate-limiting logic in the implementation is sound, but none of this sophistication is exposed to the LLM via tool descriptions or parameter guidance.

• Expand tool descriptions to 100 - 200 characters. For get_steam_item_data: 'Fetch detailed market data for a known Steam item: current price, 10-day price history, and sales volume. Requires exact item name. Use search_steam_items first if you only have a partial name.'
• Add parameter descriptions: appid: 'Steam application ID as a string (e.g., "730" for CS:GO)', item_name: 'Exact name of the item as it appears on the Steam Community Market'
• Add parameter descriptions for search_steam_items: search_term: 'Partial or full item name to search for (e.g., "AK-47")', max_results: 'Number of results to return (default 10, must be 1 - 100)'
• Document output schema for get_steam_item_data: 'Returns object with fields: item_name (string), appid (string), current_price (string, e.g. "$5.00"), exterior (string, e.g. "Factory New"), description (string), last_10_days_prices (array of {date, price, sales}), status ("success" or "partial_data"), error (string if failed)'
• Document output schema for search_steam_items: 'Returns array of item objects with fields: item_name, appid, and market_url suitable for passing to get_steam_item_data'
• Add error recovery hints: when returning an error, suggest a follow-up tool or user action. E.g., 'Item not found. Try calling search_steam_items with a partial name to see available options.'
• Add min/max bounds to max_results parameter documentation: 'Limit 1 - 100 to prevent timeout'
• Consider adding an 'error_classification' pattern: distinguish between 'retryable' (timeout, rate limit), 'user_fixable' (item not found, try search), and 'fatal' (Steam API unreachable) errors to guide agent retry logic

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry