MCP-box exposes 13 Android accessibility and device tools via HTTP. Tool naming follows verb_noun convention (accessibility/health, accessibility/click_text, etc.), which is good. However, descriptions are extremely terse (10-30 chars), parameter descriptions are entirely absent, and input schemas lack type information for most parameters. No output schemas are documented. Error handling is not visible in the provided code. The server appears to be a direct Android accessibility service wrapper without LLM-optimized tool design. Most tools lack the context needed for LLM selection and safe execution.

• Expand every tool description to 50-150 characters. Include WHAT it does, WHEN to use it, and what it returns. E.g., 'accessibility/click_text': 'Finds and clicks the first UI element containing the specified text. Use this to interact with buttons, links, or menu items by their visible label. Returns success/failure and the clicked element's resource ID.'
• Add descriptions to all parameters. For each param, state the expected format, valid values, and constraints. E.g., accessibility/scroll direction param: 'Direction to scroll: forward (down/right) or backward (up/left). Required.'
• Document output schemas for all tools. Specify the structure of responses (e.g., accessibility/ui_snapshot returns {nodes: [{id, text, bounds, clickable}], totalNodes}). This enables LLMs to extract and chain data.
• Add type declarations to optional parameters. Change accessibility/find_nodes schema from {text, viewId, limit} to {text: string, viewId: string, limit: integer} with min/max constraints.
• Implement error recovery hints. For destructive tools (click, set_text, swipe), return actionable errors: 'Text "Submit" not found. Visible buttons: ["Cancel", "Next"]. Try scrolling first or use accessibility/find_nodes to locate the target.'

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

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