Critical failure: The single tool 'anyapp_*' is dynamically discovered and registered, but no explicit tool definitions, schemas, descriptions, or parameter documentation are visible in the source code. The tool name pattern 'anyapp_*' is a wildcard prefix, not a concrete verb_noun action name. File internal/tools/anyapp_linux.go is referenced but not provided. Without visible schema definitions, parameter types, descriptions, or output documentation, this tool cannot be evaluated against quality baselines. The description provided ('Any App (Linux) tools backed by codex-computer-use-linux...') is generic and does not explain what individual tools do, when to use them, or what they return. This violates the core requirement that every tool must have a non-empty, actionable description (10-1024 chars) and documented input/output schemas.

• Provide explicit tool registration code showing concrete tool names (not wildcards), descriptions (50-200 chars), input schemas with typed parameters, and output schemas.
• Replace 'anyapp_*' wildcard with specific action names: e.g., 'execute_linux_command', 'run_app_action', 'invoke_codex_tool'. Each tool name must start with a verb.
• Document every parameter with type, description, constraints (enum, min/max, pattern), and whether it is required. Example: 'command (string, required): The Linux shell command to execute. Max 1000 chars. No sudo.'
• Add per-tool descriptions explaining what each tool does, when to use it, prerequisites, and what it returns. Minimum 50 chars, maximum 1024 chars.
• Include output schema documentation showing response structure, field types, and which fields are needed for downstream tool chaining (e.g., if a tool returns an ID, document it so agents can pass it to other tools).