PHP MCP Server has significant definition quality gaps. Of 8 tools, 2 lack descriptions entirely (echo_text, hidden_subdir_tool), 3 have minimal/generic descriptions under 50 chars. Naming is inconsistent: some tools use verb_noun (process_data_by_mode, greet_user), others use camelCase (repeatAction, InvokableCalculator). Only 3 tools have complete input schemas with typed parameters and descriptions. Parameter descriptions are sparse, most tools lack per-parameter documentation. No output schemas are documented. Error handling is absent from all tool definitions. The framework supports tool annotations (McpTool attribute), but only 1 tool demonstrates usage. Overall, definitions lack the LLM-optimization and completeness required for reliable agent selection and execution.

• Add descriptions to all 8 tools. Minimum 50 chars, maximum 200 chars. State WHAT the tool does, WHEN to use it, and what it returns. Example: 'Greets a user by name and returns a personalized greeting message. Use when you need to acknowledge a user in a conversation.'
• Standardize naming to snake_case verb_noun convention (e.g., repeat_action, invoke_calculator). This matches 90% of production tools and helps LLMs parse intent from names alone.
• Document output schemas for all tools. Specify field names, types, and whether results are paginated. Example for calculator: 'Returns {result: number, operation: string, a: number, b: number}'.
• Add per-parameter descriptions for all parameters. For enums like 'mode', explain what each option does. Example: 'mode (enum: OptionA=standard processing, OptionB=advanced processing)'.
• Implement error handling patterns: categorize errors as retryable vs fatal, include the invalid value in error messages, and provide recovery hints. Example: 'Invalid mode: got "OptionC", must be OptionA or OptionB.'

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

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