adbfriend has 5 tools with mixed quality. Tools are visible in source code (Sync.kt, Uninstall.kt, Packages.kt, AdbSpeed.kt, Test.kt), so they are not inferred. However, critical issues severely limit quality: (1) Naming is weak, tools lack clear action verbs. 'sync' is acceptable, but 'adb_speed' is vague (should be 'get_device_usb_speed' or 'check_adb_speed'), 'test' is generic, 'packages' should be 'manage_packages' or split into separate tools (force_stop_packages, clear_app_cache, etc.). 'uninstall' is clear but lacks specificity (uninstall_packages would be better). (2) Descriptions exist but are sparse (10-100 chars) and lack LLM guidance. 'Executes various test operations' tells the LLM nothing about WHEN to use it or WHAT it returns. 'Prints the USB speed' is too narrow. (3) Input schemas are present for 3 tools (sync, uninstall, packages) with typed parameters and descriptions, this is good. However, 'adb_speed' and 'test' lack visible schemas in source. (4) Output schemas are not documented for any tool, the rubric requires documentation of what these tools return. (5) Error handling is absent, no guidance on what happens on failure or how to recover. (6) No tool annotations (readOnlyHint, destructiveHint). Tools like 'uninstall' (DESTRUCTIVE) and 'sync' (WRITE) need explicit risk annotation. (7) Composition issues: 'packages' combines three separate concerns (force_stop, clear cache, set immersive.full) into one tool, should be split per pattern:tool. Sync has many options that could be separate tools. (8) Parameter quality is mixed: sync has good descriptions and types, but 'packages' parameter in packages tool is just a string filter, ambiguous whether it matches package name, substring, or glob. (9) Test tool has no visible parameter schema and vague description. Average tool score: 38/100.

• Add JSON output schemas for all tools. Document field names, types, and structure. E.g., sync returns: {synced_files: [string], deleted_files: [string], failed: [{file: string, error: string}], total_time_ms: long}
• Rename tools to action verbs: adb_speed → get_device_usb_speed, test → run_device_tests, packages → manage_packages (or split).
• Add toolAnnotations: mark uninstall, sync (with deleteMissing), and packages (with clear) as destructiveHint=true. Mark adb_speed and test as readOnlyHint=true.
• Split 'packages' tool into three: force_stop_packages(packages, force), clear_package_data(packages, force), set_package_immersive(packages, enabled).
• Clarify 'packages' parameter matching logic in descriptions. E.g., 'packages: Glob pattern or substring match (e.g., "com.google.*", "gmail"). Matches all installed packages. Required.'
• Add per-tool error handling. E.g., sync: 'If push times out (pushTimeout exceeded), retry with exponential backoff or ask user to reduce file size. If device offline, return error with available devices.' uninstall: 'If package not found, return available installed packages matching the pattern.'
• Expand descriptions to 100-200 chars with WHEN, WHAT, and RETURN. E.g., test: 'Run automated tests on connected Android devices. Use this to validate builds before release. Specify test_type to select which test suite (unit, integration, e2e). Returns test_results with counts, logs, and device_id.'
• Add parameter validation rules to descriptions. E.g., 'packages: One of: (1) exact package name (com.example.app), (2) glob pattern (com.example.*), (3) substring (gmail). Case-sensitive. Matches up to 100 packages; if more match, call list_packages first to narrow.'

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

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