This server provides 5 tools with reasonable naming and enum-constrained parameters. Tool descriptions are present and mostly adequate (100-250 chars), meeting the 10-1024 char baseline. However, parameter descriptions are sparse or missing entirely on several tools, and output schemas are not documented. The server implements error handling via degraded-mode credential gating (tb_login), but lacks per-tool recovery guidance. Schemas are visible as Zod-style dicts with type constraints, but output structure documentation is absent. No tool annotations (readOnlyHint, destructiveHint) are declared despite clear read/write semantics. The design is reasonably idempotent and uses action verbs (upload, run, get), but lacks explicit per-parameter descriptions for optional parameters.

• Document output schemas for all tools. Example: 'uploadAppAutomateApp returns {projectId: number, status: string, expiresAt: string}' or embed a response example in the description.
• Add per-parameter descriptions for optional parameters in runAppAutomateTest. For each of testClasses, skipTestClasses, packages, annotations, testRunner, describe when to use it, expected format (fully qualified class names, package name patterns, annotation syntax), and provide an example or reference to TestingBot docs.
• Declare tool annotations in the tool registration. Mark uploadAppAutomateApp and uploadAppAutomateTests with destructiveHint=true; mark getAppAutomateRunStatus with readOnlyHint=true; mark tb_login with idempotentHint=true.
• Add constraint guidance to runAppAutomateTest parameter descriptions. For deviceName, document the regex/wildcard syntax explicitly: 'Device name pattern supporting wildcards (e.g. "*") and regex ranges (e.g. "iPhone 1[4-6]")'. For testRunner, specify expected format (e.g., 'Android instrumentation runner class name, e.g. "androidx.test.runner.AndroidJUnitRunner"').
• Document error scenarios in tool descriptions. E.g., 'uploadAppAutomateApp may fail if: file does not exist (suggest checking localFilePath), file is >500MB (suggest splitting tests), or authentication fails (ensure tb_login succeeded). Poll with getAppAutomateRunStatus if the upload succeeds but the run does not start immediately.'
• Add a note to tb_login description or to runAppAutomateTest/uploadAppAutomateApp that these tools require prior authentication via tb_login, or mention the credential degradation behavior upfront.

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

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