SeiTrage has 6 tools with severe definition gaps. Only 2 tools (createDocument, updateDocument) have descriptions; 4 tools (getWeather, getBalance, transferSei, requestSuggestions) lack descriptions entirely. No input schemas are visible in the provided source code for any tool. Tool names are verb-based (good), but without schemas and descriptions, LLMs cannot reliably select or invoke these tools. The codebase shows tool definitions in app/api/chat/route.ts but the actual schema definitions are not included in the provided excerpt, making it impossible to verify parameter types, constraints, or output structures. This is a critical blocker for production use.

• Add non-empty descriptions to all 6 tools. For getWeather: 'Retrieves current weather conditions for a specified location. Returns temperature, humidity, and forecast.' For getBalance: 'Fetches the current Sei token balance for the connected wallet. Returns balance in SEI units.'
• Document complete input schemas in code with JSON Schema format. Every parameter must have a 'type' and 'description' field. Example: {"location": {"type": "string", "description": "City name or coordinates (lat,lon)"}}
• For transferSei, add a dry-run parameter and explicit confirmation step. Description should state: 'Transfers SEI tokens to a recipient address. This is irreversible, use with caution. Requires explicit confirmation.'
• Document output schemas for all tools. Example for getBalance: {"balance": {"type": "string", "description": "Balance in SEI units"}, "wallet_address": {"type": "string", "description": "Connected wallet address"}}
• Add error handling guidance. For transferSei: 'If insufficient balance, returns error with available balance. If network fails, returns retryable error with timeout guidance.'

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

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API