Three tools with complete input schemas and descriptions, but quality is uneven. All tools have regex-validated Hedera ID parameters and numeric defaults. Descriptions are adequate (40-60 chars) but lack actionable context about when to use each tool or what happens on failure. No output schema documented. No error handling guidance. Tools follow verb_noun naming but lack distinction in descriptions, LLMs may conflate swap operations. Missing parameter descriptions for some fields (e.g., what 'slippageTolerancePercent' means in practice, why 0.5% default). No mention of prerequisites (e.g., user must have token balance, account setup). Schemas are well-formed with Zod validation, but responses are raw JSON without field documentation.

• Document the SwapResult output schema with field names, types, and descriptions. Example: { transactionId: string, outputAmount: string, actualSlippage: number, timestamp: ISO8601 }. This enables LLMs to extract and chain results.
• Expand tool descriptions to 150-250 chars. Include: what the tool does, when to use it vs alternatives, prerequisites (e.g., 'Requires token association on account'), and what happens on failure. Example: 'Swaps HBAR for an HTS token on SaucerSwap. Use this when you have HBAR and want a specific token. Requires the token to be associated with your account. Returns transaction ID and actual output amount. Fails if slippage exceeds tolerance or deadline passes.'
• Add constraint descriptions to parameters. For slippageTolerancePercent: 'Max allowed slippage as a percentage (0-100). If actual slippage exceeds this, the transaction reverts. Default 0.5% is conservative; increase for volatile pairs.' For deadlineSeconds: 'Transaction must complete within this many seconds from submission, or it reverts. Default 300s (5 min) is typical; increase for congested networks.'
• Implement error classification in tool responses. Return structured errors with category (retryable|user_fixable|fatal), message, and recovery hint. Example: { error: 'insufficient_balance', category: 'user_fixable', message: 'Account has 5 HBAR but swap requires 10 HBAR', hint: 'Deposit more HBAR or reduce swap amount' }.
• Add a discovery tool or resource listing available token pairs and their liquidity. This helps LLMs validate token IDs before attempting swaps and reduces failed calls.

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

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