No output schemas documented in source code. Tools like pageStack, testAccounts, currentPage, systemInfo return unstucured data with no schema definition visible. LLMs cannot plan downstream calls without knowing response structure.

Parameters with 'any' type lack proper constraints. evaluate.appFunction accepts 'string', but evaluate.args accepts 'array' with no element type. exposeFunction.bindingFunction is typed 'any'. These invite hallucinated or invalid inputs from LLMs.

No error handling guidance visible. Tools like launch, navigateTo, evaluate, and callWxMethod perform complex operations but provide no recovery instructions if they fail. LLMs receive errors with no guidance on whether to retry, ask user, or escalate.

Tool dependencies are documented in the prompt but NOT in individual tool descriptions. LLMs reading tool help will not see that launch is a prerequisite for all others. Dependencies should be stated in each tool's description.

Parameter constraints poorly documented. 'type' in getlogs is described as 'log、info、warn、error、debug', should be an enum constraint, not a prose list. 'limit' has no range (min/max). 'delta' in navigateBack has no range.

No idempotency or side-effect clarity. Tools like setPageData, callWxMethod, exposeFunction, mockWxMethod modify state but descriptions do not warn LLMs of retry risks. Should state if operations are idempotent or irreversible.

Parameter ambiguity: navigateTo, redirectTo, reLaunch, switchTab all take 'url' but there is no validation or format constraint shown. Should clarify: must start with '/'? Are query params supported? Can relative paths be used?

Selector parameter in getElement, getElements lacks examples of valid CSS selector syntax. Documentation is minimal: 'supports CSS selectors', but LLMs may not know valid syntax. Should include examples or link to selector reference.

waitFor.condition parameter accepts 'any' type covering both selector strings and functions. No clarity on how functions should be passed (code string? JSON? object?). Highly ambiguous for LLMs.

getPageData.path parameter has no type definition in visible schema. Described as supporting dot notation (user.info.name) but no validation rule documented. What happens if path doesn't exist?