Nexus defines 5 tools with explicit schemas and descriptions visible in src/agent/loop.ts. All tools have names starting with action verbs (get_, emit_) and descriptions (10-100 chars). However, parameter descriptions are sparse or missing: get_transfer_overview, get_large_transfers, and get_chain_netflows have empty input schemas with no documented parameters. get_transfer_detail has a transfer_id parameter with a description. emit_anomaly has 6 parameters with type enums and descriptions. Output schemas are not documented anywhere in the source. Error handling is absent, no recovery guidance, no categorization of errors, no actionable error messages. The tool set is well-composed (each does one thing), but lacks the depth of documentation and error handling expected in production tools.

• Document output schemas for all 5 tools. Specify field names, types, and what data each field contains. Example: get_transfer_overview returns {totalTransfers: number, largeTransfers: number, solanaNetUsd: string, stablecoinShare: number}.
• Add parameter descriptions to get_transfer_overview, get_large_transfers, and get_chain_netflows. Even if they accept no inputs, document this explicitly: 'This tool takes no parameters. Call it to retrieve a summary of all bridge transfers in the current cycle.'
• Implement error handling with recovery guidance. Return structured errors like {error: 'transfer_not_found', transfer_id: '...', suggestion: 'Call get_transfer_overview to see available transfers'}.
• Add a dry-run parameter to emit_anomaly or create a separate confirm_anomaly tool. Let agents preview the anomaly before flagging it, reducing false positives.
• Create a list_transfers or search_transfers discovery tool to help agents find transfer IDs before calling get_transfer_detail. Return paginated results with transfer_id, fromChain, toChain, amountUsd, and txHash.

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

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