27 tools with significant quality gaps. Most tools have basic descriptions (10-50 chars) but lack depth on WHEN to use them or prerequisites. Parameter descriptions are minimal ('Token ID', 'Amount') without format/range guidance. No output schemas documented. Many parameters use z.any() instead of proper type constraints, violating schema rigor. Error handling is absent, no recovery guidance, no categorization. Naming is verb-noun compliant but generic (get_*, create_*, etc.). No tool annotations (readOnlyHint, destructiveHint). Composition is reasonable, tools are single-purpose, but chaining IDs are not consistently returned.

• Replace z.any() with explicit Zod schemas for protocol, metadata, slippage. E.g., protocol: z.union([z.object({btc: z.null()}), z.object({eth: z.null()})]) to constrain valid options.
• Document output schemas for all tools. E.g., canister_getBalance returns {balance: string, tokenId: string, account: string, network: string}. Include chaining IDs (tokenId, account) for downstream tool calls.
• Expand parameter descriptions to 50-100 chars with format/range. E.g., 'Amount (string, must be convertible to BigInt; e.g., "1000000000")' instead of 'Amount (string, needs to be converted to BigInt)'.
• Add tool annotations: mark canister_withdraw, canister_createToken, canister_*Trade, canister_*Liquidity, odinapi_identity_postComment with destructiveHint=true; mark all read-only tools with readOnlyHint=true.
• Implement error handling with recovery guidance. E.g., on withdrawal failure: 'Withdrawal failed: insufficient balance. Call canister_getBalance to verify funds before retrying.' Categorize errors as retryable vs user-fixable.

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

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