Single tool with a problematic interface. Tool name is descriptive (calculate_poker_odds), but description is in Chinese, making it inaccessible to most English-speaking LLMs and developers. Input schema is present and typed, but parameters have minimal English descriptions, only Chinese annotations are visible in the code. The schema structure is reasonable (array of hand strings, optional community cards, simulation count), but lacks actionable guidance for LLM selection and error handling. No output schema is documented. Error handling is present in the core function but returns generic error dicts without recovery guidance. The tool does one thing (calculate odds), which is good for composition, but the description quality and parameter clarity are below production standards.

• Rewrite tool description in English: 'Calculate win/loss/tie probabilities for Texas Hold'em poker hands given known community cards. Supports 2 - 9 players. More simulations (default 10000) yield more accurate odds.'
• Translate all parameter descriptions to English and add format/constraint details. E.g., 'player_hands: Array of hand strings (2 cards each, e.g., ['AsKd', '7c8h']). Ranks: 2-9, T, J, Q, K, A. Suits: h(hearts), d(diamonds), s(spades), c(clubs). Supports 2 - 9 players.'
• Add output schema documentation (e.g., in docstring): 'Returns {player_odds: [{player_index: int, win_prob: float, loss_prob: float, tie_prob: float}, ...], num_simulations: int} or {error: str}.'
• Enhance error messages with recovery guidance. E.g., instead of raising 'Invalid hand format', return {error: 'Invalid hand format in hand_str. Each hand must be exactly 2 cards in rank+suit format (e.g., AsKd). Ranks: 2-9, T, J, Q, K, A. Suits: h, d, s, c.'}
• Add maximum simulation count constraint (e.g., 1000000) and document it: 'num_simulations: Integer, 100 - 1000000. Default 10000. Higher values increase accuracy but may cause longer computation times.'
• Clarify what happens if community_cards is omitted: 'If community_cards is not provided, all 5 community cards will be simulated. If provided as 3 cards (flop) or 4 cards (turn), the remaining cards will be simulated from the deck.'
• Add tool annotation hints in the description: mark this as a safe, read-only, idempotent operation (same inputs always produce same odds, within simulation variance).