6 tools with basic schemas and descriptions, but significant gaps. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization). Input schemas present but minimal, most parameters lack descriptions. No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Naming is verb-forward (fork, kill_fork, send_raw_tx, snapshot, revert, list_forks) but descriptions are terse and lack context on when to use each tool or what they return. Parameters like 'chain', 'id', 'rawTx' have no descriptions in the visible schema. No pagination, no structured output guidance.

• Add parameter descriptions to all tools. For 'fork': describe 'chain' as enum (ethereum|berachain|arbitrum|base|...), 'block' as string (block number or 'latest'), 'rpcUrl' as optional override. For 'send_raw_tx': describe 'id' as fork ID (from fork tool), 'rawTx' as hex-encoded signed transaction.
• Document output schemas for each tool. E.g., fork returns {fork_id: string, rpc_url: string}; snapshot returns {snapshot_id: string}; list_forks returns {forks: [{id: string, chain: string, block: string, rpc_url: string}]}. Include these in tool definitions so agents know what to extract.
• Expand descriptions to 50-200 chars with context. E.g., 'fork': 'Spin up a local Anvil fork of the given chain at a specific block. Returns fork ID and RPC URL for use in send_raw_tx and other fork operations. Requires Anvil installed locally.' Include when to use (e.g., 'Use before send_raw_tx to test transactions in isolation').
• Add tool annotations (destructiveHint, idempotentHint) to schema. Mark fork, kill_fork, send_raw_tx, revert as destructiveHint=true. Mark snapshot, list_forks as readOnlyHint=true. Mark fork, snapshot, revert as idempotentHint=true (safe to retry). This enables agents to reason about retry safety.
• Add error handling guidance. E.g., send_raw_tx: 'Returns error if fork ID not found (call list_forks to verify) or transaction is invalid (check rawTx format). Errors are retryable if transient (network timeout) or fatal if validation fails (malformed tx).' Include recovery steps for each error class.