7 tools with HTTP transport and explicit schema definitions. Most tools have descriptions and parameter schemas, but several critical gaps exist: (1) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear categorization of WRITE vs READ_ONLY risk levels; (2) Parameter descriptions exist but are often terse (under 40 chars) and lack actionable guidance; (3) No documented output schemas, responses are not formally specified; (4) No error handling documentation or recovery guidance; (5) Tool names follow verb_noun pattern but some are domain-specific (amiga_*) which is appropriate but narrows discoverability. The amiga_watch_logs tool has streaming semantics (returns after duration_ms) but this is not reflected in output schema. The amiga_inspect_memory tool lacks max value constraints on the 'size' parameter despite mentioning max 4096.

• Add tool annotations: mark amiga_build, amiga_clean, amiga_connect, amiga_disconnect with destructiveHint=true; mark amiga_watch_logs, amiga_log, amiga_inspect_memory with readOnlyHint=true. Mark idempotent tools (amiga_log, amiga_inspect_memory) as idempotentHint=true.
• Document output schema for each tool. For example, amiga_log should specify: returns {messages: [{level: string, timestamp: string, text: string}], total: number, count: number}. This enables LLMs to know what to extract.
• Expand amiga_disconnect description from single sentence to: 'Disconnect from the currently active Amiga serial connection (PTY or TCP). After calling, amiga_build and amiga_inspect_memory operations will fail until reconnected via amiga_connect. Returns {status: "disconnected", was_mode: "pty"|"tcp"}.'
• For amiga_build and amiga_clean, clarify parameter description: 'Subpath relative to repository root, e.g. "examples/hello_world". Omit or pass empty string to build all projects.'
• For amiga_inspect_memory, add explicit maximum constraint in schema: {"size": {"type": "number", "description": "Number of bytes to read (max 4096)", "maximum": 4096}}
• For amiga_watch_logs, document what a log notification contains and whether the tool returns a summary after streaming. E.g., 'Streams messages via MCP notifications with {level, timestamp, text} fields. Returns {notifications_received: number, duration_ms: number} after the watch window closes.'
• Add error handling guidance to descriptions. For amiga_inspect_memory: 'If address is invalid or read fails, returns {error: string, address: string, reason: string}. Retry with adjacent address or request system_log to diagnose.'

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

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