All 7 tools have empty input schemas (type:object, properties:{}), making them non-functional. Descriptions are present but generic (10-60 chars), lacking WHAT/WHEN/HOW context. No parameter documentation exists. Tools exhibit multiple responsibilities (e.g., collateral-mover supplies AND withdraws; report-fetcher pulls AND evaluates). No output schemas documented. No error handling guidance. This server is an audit target, not a production tool, but the tool definitions themselves are severely deficient.

• Define input schemas for each tool. E.g., comet-state-reader should accept {"market_address": {"type": "string", "description": "Comet market contract address (0x...)"}, "account": {"type": "string", "description": "User account address to query"}}.
• Document output schemas. E.g., comet-state-reader returns {"supply_balance": number, "borrow_balance": number, "collateral_value": number, "market_state": {...}}.
• Expand descriptions to 100-200 chars with WHAT/WHEN/HOW. E.g., 'Read the current supply and borrow balances for a user account in a Comet market. Call this first to check collateral before attempting rebalance-exec. Returns balances in wei and market state (rates, utilization).'
• Split multi-purpose tools: collateral-mover → supply_collateral + withdraw_collateral; report-fetcher → fetch_reports + evaluate_reports. Each tool should do one thing.
• Add error handling guidance to descriptions. E.g., 'If RPC endpoint is unreachable, retry with exponential backoff. If account not found, verify the address is checksummed.'