Syntra AI MCP provides 13 blockchain query tools with complete input schemas and reasonable descriptions. All tools are READ_ONLY and follow a consistent naming pattern (verb_noun: txn_by_id, erc20_transfers, etc.). However, descriptions are brief (avg ~80 chars, below the 194-char baseline for A+ tools) and lack context on WHEN to use each tool or dependencies between them. Parameter descriptions are present but minimal. Output schemas are not documented, critical for LLM planning. No error handling guidance, no pagination info despite tools returning potentially large result sets. Tool names like 'blocks_transactions_hashes' and 'erc20_transfers_and_approvals' violate single-responsibility principle (contain 'and'). Missing tool annotations (readOnlyHint present via Risk field, but not in schema).

• Expand tool descriptions to 150 - 250 chars. Include WHEN to use (e.g., 'Use this to fetch a single transaction by hash when you know the exact tx ID. For multiple transactions, use wallet_activity or blocks_and_transactions.').
• Split compound tools: rename 'blocks_transactions_hashes' → 'get_blocks' + 'get_transaction_hashes'; 'erc20_transfers_and_approvals' → 'get_erc20_transfers' + 'get_erc20_approvals'.
• Document output schemas for each tool. Specify which fields are returned (e.g., block_data returns {block_number, timestamp, transactions: [{hash, from, to, value}], logs: [...]}) so LLMs can chain calls.
• Add pagination: include limit (default 20, max 100) and offset/cursor parameters. Return total_count and next_cursor in responses to guide multi-page queries.
• Add error handling guidance: document what happens on invalid inputs (e.g., 'Invalid block range: from_block must be ≤ to_block and ≤ current height. Current height: 19500000.').