Scoring was not performed

• Rename 'tool_name' to a specific action verb + noun (e.g., 'analyze_stock', 'fetch_market_data', 'calculate_technical_indicator'). The current name is a placeholder and provides no semantic meaning.
• Rename 'public_tool_name' to reflect its actual function (e.g., 'search_public_stocks', 'get_market_overview'). 'Public' is a permission descriptor, not an action.
• Expand descriptions to 50-200 characters with WHAT the tool does, WHEN to use it, and WHAT it returns. Example: 'Fetch real-time stock data for a given ticker symbol. Returns current price, 52-week range, market cap, and volume. Use this to get up-to-date market information before analysis.'
• Document output schema for each tool. Specify field names, types, and presence (required vs optional). Example: '{"ticker": string, "price": float, "change": float, "volume": integer, "timestamp": iso8601}'
• Replace placeholder parameter descriptions. 'param1' should become something like 'stock_ticker' with description 'Stock symbol (e.g., AAPL, GOOGL), 1-5 uppercase letters'.
• Add parameter constraints where applicable: enum values for status/type fields, min/max for numeric ranges, regex patterns for IDs/codes, required vs optional flags.
• Document error cases and recovery guidance. Example: 'If ticker not found, search_stocks() with company name. If API rate limit hit, retry after 60 seconds.'
• Move tool definitions out of templates directory into actual implementations. The current structure suggests these are not real, functional tools.