phpMan defines 2 tools with reasonable naming (cli_help, cli_search) and complete input schemas. Both descriptions are present and moderately detailed (150-200 chars), exceeding the 20-char minimum. However, parameter descriptions lack specificity about format constraints, valid ranges, and error recovery guidance. Output schemas are not documented in the visible code. Error handling is minimal, no guidance on what to do if a command is not found or search returns no results. The tools follow a single-responsibility pattern (help vs search) but lack the LLM-optimized descriptions and comprehensive error recovery patterns expected of production-grade tools.

• Document output schemas for both tools. For cli_help, specify: {sections: [{name, subsections: [string]}], synopsis: string, content: string}. For cli_search, specify: {results: [{name, section, description, link}], total_count: number}.
• Add format constraints to parameters. For 'command': 'Unix/Linux command name or module (1-100 chars, alphanumeric + special chars like ::, #, -)'. For 'section': 'Manual section number (1, 2, 3, 3pm, 8, etc.) or omit for auto-detection'.
• Implement pagination for cli_search: add 'limit' (1-100, default 20) and 'offset' (default 0) parameters. Return total_count in response so LLMs know if more results exist.
• Add error recovery guidance to descriptions. E.g., cli_help: 'If command not found, try cli_search() with a keyword. Returns structured sections (SYNOPSIS, DESCRIPTION, OPTIONS, EXAMPLES).'
• Remove example values from descriptions and replace with formal constraints. E.g., instead of 'e.g. File::Basename', use enum or pattern validation in schema.