amule-mcp has 6 tools with basic schemas and descriptions, but significant gaps limit production readiness. Tool names follow verb_noun convention (amule_status, amule_search, amule_download, ec_raw, amule_files, amule_queue), which is good. However, descriptions are inconsistent in depth and actionability. amule_search has a detailed description explaining scope/filtering; amule_status and amule_queue are terse. Parameter descriptions exist but lack constraint details (e.g., no min/max for limit, no enum for scope despite mentioning valid values). Output schemas are not documented, responses are inferred from code (dicts with 'raw', 'error', 'results' fields). Error handling is minimal: ec() raises RuntimeError with truncated output; no recovery guidance. No tool annotations (readOnlyHint/destructiveHint). amule_download is marked WRITE but lacks confirmation/dry-run pattern. Overall, definitions are functional but below production baseline (194 char avg description; 100% of A+ tools have param descriptions, this server has ~70%).

• Document output schemas for all tools. Add a docstring or inline comment showing the return type and field descriptions. E.g., amule_search returns {query: str, scope: str, total_found: int, after_filter: int, results: [{n: int, name: str, size: str, sources: int}], raw: str}.
• Add enum constraints to parameters. Change 'scope' description to include 'enum: ["global", "kad", "local"]' in schema. Add min/max to 'limit' (1 - 50) and 'min_mb'/'max_mb' (0 - 10000).
• Enhance error messages with recovery guidance. Instead of 'amulecmd rc=1: ...', return 'Failed to connect to aMule at amule:4662. Check AMULE_HOST and AMULE_EC_PWD environment variables. Ensure amule-daemon is running.'
• Expand terse descriptions. amule_files: 'List all files currently downloading or queued, with version-tolerant parsing to handle different aMule versions. Use this to monitor download progress.' amule_queue: 'Show the download queue with per-file progress, speed, and ETA when available. Call this to check active downloads and their status.'
• Add tool annotations. Mark amule_status, amule_search, ec_raw, amule_files, amule_queue with readOnlyHint=true. Mark amule_download with destructiveHint=true and add a dry_run parameter or confirmation step.