27 tools with complete naming (verb_noun pattern) and descriptions present. However, critical gaps undermine quality: (1) Parameter descriptions are minimal or generic, most lack format/constraint details required by pattern:constrained-input. E.g., 'counterparty' appears in 15+ tools described only as 'hex pubkey, "self", or "anyone"' with no validation guidance. (2) Output schemas are entirely undocumented, no tool declares what fields it returns, violating pattern:tool and pattern:response-shaper. (3) Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. (4) Complex nested parameters (e.g., 'outputs' array with object items in createAction) lack schema detail. (5) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Naming is strong (all verb-prefixed, clear intent), but parameter and output documentation is production-incomplete.

• Document output schema for every tool. Include field names, types, and descriptions. Example: 'Returns {publicKey: string (66-char hex), derivationPath: string, timestamp: ISO8601}'. This enables LLM planning and data extraction.
• Add format/constraint details to parameter descriptions. Replace 'counterparty: hex pubkey, "self", or "anyone"' with 'counterparty: 66-char hex compressed pubkey (e.g., 02abc...), literal string "self", or literal string "anyone". Invalid values return HTTP 400 with constraint details.'
• Add error handling guidance to WRITE tools (createAction, signAction, abortAction, etc.). Example: 'On HTTP 409 (action already signed), call abortAction and retry. On HTTP 422 (invalid outputs), fix the output array and retry. On HTTP 500, wait 5s and retry.'
• Annotate tools with readOnlyHint, destructiveHint, idempotentHint in tool definitions. Example: {name: 'createAction', inputSchema: {...}, readOnlyHint: false, destructiveHint: true, idempotentHint: false}.
• Define nested object schemas explicitly. For 'outputs' array in createAction, specify: 'Array of objects, each with {lockingScript: string (hex), satoshis: integer (>0), outputDescription: string (optional)}'. For 'fields' in acquireCertificate, specify allowed keys and value types.

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

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