Three tools with minimal documentation. Descriptions are present but generic (18-50 chars, below 20-char threshold for 'browser'). 'exec_command' has a single parameter with type but no description. No output schemas documented. No error handling guidance. Tools appear inferred from code rather than explicitly registered with full MCP definitions.

• Add explicit input schemas to 'browser' and 'computer' with typed parameters and descriptions. Example: {"type": "object", "properties": {"session_id": {"type": "string", "description": "Unique browser session identifier"}}, "required": ["session_id"]}
• Expand 'browser' description from 18 to 50-100 characters. Include WHAT it does, WHEN to use it, and what it returns. Example: 'Manage browser automation tasks: start sessions, navigate URLs, capture screenshots, interact with page elements. Use for web scraping, testing, or user-facing workflows.'
• Add description to 'exec_command' cmd parameter: 'Shell command to execute (bash/sh syntax). Max 4096 chars. Avoid interactive prompts; use non-interactive flags. Returns stdout, stderr, and exit code.'
• Document output schemas for all three tools. Example for exec_command: {"type": "object", "properties": {"stdout": {"type": "string"}, "stderr": {"type": "string"}, "exit_code": {"type": "integer"}}}
• Add error handling and confirmation patterns. For IRREVERSIBLE tools like exec_command, support a dry_run parameter or require explicit confirmation before executing destructive commands.