Single tool 'ToolSearch' has a reasonable description (89 chars) and valid JSON Schema with typed parameters. However, the schema lacks parameter descriptions, critical for LLM understanding. The tool name 'ToolSearch' is generic and does not follow verb_noun convention (should be 'search_tools'). No output schema is documented. The server appears to be a reconstructed/restored codebase with incomplete MCP integration, tool definitions are inferred from Go code rather than explicitly registered via MCP protocol.

• Rename 'ToolSearch' to 'search_tools' to follow verb_noun convention and clarify intent to LLMs.
• Add descriptions to all input parameters: 'query' (e.g., 'Keywords or exact tool names to search for. Use "select:ToolName" for exact-name lookup, or pass keywords to rank by prefix and substring match.') and 'max_results' (e.g., 'Maximum number of results to return (1-50). Defaults to 20.').
• Document the output schema explicitly: describe the structure of returned tool objects (name, description, schema, risk level, etc.) so LLMs know what fields to expect.
• Add error handling guidance: 'If no tools match, return an empty list with a note suggesting broader keywords or checking CLAUDECODE_TOOLS environment variable.'
• Clarify the 'select:' syntax in the description with an example: 'Use select:ToolSearch,ToolRegistry to look up exact tool names; omit select: to search by keyword.'