Flow MCP server has 9 tools with complete input schemas and descriptions, but quality is inconsistent. Tool names follow verb_noun convention (get_*, send_*, resolve_*, execute_*, find_). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameters lack depth: no enums for network selection, no format constraints, no validation guidance. Critical security issue: send_transaction exposes signerPrivateKey as a parameter, this violates secret-injection pattern and will leak credentials into logs. Output schemas are undocumented. Error handling is minimal. Most tools are read-only (8/9), reducing risk, but composition and chaining support is weak.

• Move signerPrivateKey to server-side configuration. Accept only signerAddress as a parameter. Load the private key from an environment variable or secure vault inside send_transaction.
• Document output schemas for all 9 tools. Specify which fields are returned, their types, and which IDs/references can be chained to other tools.
• Add enum constraint to network parameter: {"enum": ["mainnet", "testnet"]} to prevent invalid network names.
• Expand tool descriptions to 100-200 chars. Include when to use each tool and how it differs from similar tools (e.g., 'Get FLOW token balance only; for other tokens, use get_token_balance with a tokenIdentifier').
• Add error recovery guidance. When resolve_domain fails, return 'Domain not found. Verify the domain ends with .find or .fn and the name is registered.' When execute_script fails, include the Cadence error and suggest checking script syntax.