Single tool 'meta_tool' lacks proper tool registration and schema documentation. The tool definition exists in lib/plugins/ai-plugin/tools/meta_tool.js but cannot be directly verified from the provided code snippet. The input schema provided is present but the tool itself appears to be a wrapper/dispatcher rather than a well-defined atomic tool. The schema includes action, tool_name, tools array, and schema object parameters, but lacks clear output documentation. Tool serves as a meta-layer to discover and call other tools dynamically, which violates the single-responsibility principle (pattern:tool). Description is lengthy (246 chars) and in Chinese, making it harder for English-language LLMs to parse intent. No evidence of proper error handling with recovery guidance, no confirmation patterns for destructive operations, and no documented output structure.

• Translate tool description to English and trim to 80-150 characters. Target: 'Discover available tools and execute them dynamically. Call list for available tools, query to inspect parameters, and call to execute.'
• Document output schema for each action: list→{tools: [{name, description, params}]}, query→{tools: [{name, schema: JSONSchema}]}, call→{result: any, error?: string}
• Add explicit error handling: 'If tool_name is not found in list action, returns {error: "Unknown tool. Available: [list]"}. If call fails, returns {error: "<reason>", retry: boolean}'.
• Remove meta-tool indirection. Instead, register individual tools (replace, bash, tts_speech) directly with their own schemas. Reserve meta_tool only for dynamic discovery if truly necessary, but expose canonical tools to agents.
• Add parameter constraints: action enum defaults already present, but add 'tool_name: required when action is call or query', 'tools: array of 1-50 strings when action is query', 'schema: valid JSON object matching queried tool schema when action is call'.
• Add composition example: 'To run bash: (1) Call meta_tool with action=list to see available tools. (2) Call meta_tool with action=query, tools=["bash"] to get parameter schema. (3) Call meta_tool with action=call, tool_name="bash", schema={cmd: "..."}.'
• Consider idempotency note: 'Query and list actions are read-only and safe to retry. Call actions may modify state, verify tool documentation before retry.'
• Add rate limiting and timeout guidance: 'Tool calls timeout after 30s. Large schema queries may take 5-10s. Rate limit agent to 10 calls/minute per tool to prevent runaway execution.'

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

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