Marketsmith provides 5 well-named, read-only tools with clear descriptions (avg 85 chars) and complete input schemas. All parameters are typed and described. However, output schemas are not formally documented in the code, only inferred from docstrings. Error handling is minimal (only get_odds and compute_ev return error objects). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Parameter descriptions lack format constraints (e.g., fee_fraction range, probability bounds). Missing pagination guidance for search_markets despite potentially large result sets.

• Add formal output schemas to each tool definition. Use JSON Schema to document return object structure, field types, and required fields. Example: search_markets returns {query: string, count: int, results: [{venue, ticker, question, yes_bid, yes_ask, no_bid, no_ask, volume, yes_implied_probability}]}.
• Annotate all tools with readOnlyHint=true in the MCP tool definition. This signals to agents that these tools are safe to retry and have no side effects.
• Add numeric constraints to parameter descriptions: 'fee_fraction: Trading fee as fraction of contract price (0.0 - 1.0, default 0.0)' and 'your_probability: Your estimate of YES outcome (0.0 - 1.0, required)'.
• Implement pagination for search_markets: add optional limit (default 20, max 100) and offset parameters. Return {query, count, total, offset, limit, results} to enable multi-page iteration.
• Add error handling to find_arbitrage and suggest_kelly. Return {error: 'market not found: {venue}:{ticker}'} if a referenced market does not exist, matching the pattern in get_odds and compute_ev.