Three well-named, read-only tools with clear descriptions and complete input schemas. Naming follows verb_noun pattern (search_datasets, query_layer, layer_info). Descriptions are substantive (120 - 180 chars) and explain purpose and data flow. All parameters have type definitions and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for downstream planning. Error handling is minimal (generic HTTP status errors). No parameter validation guidance (e.g., SQL injection risk in 'where' clause). Missing idempotency hints and rate-limit documentation.

• Document output schemas for all three tools. Example for search_datasets: 'Returns {total: number, count: number, datasets: [{id, name, summary, org, org_id, record_count, type, url}]}'.
• Add SQL injection warning to query_layer 'where' parameter: 'SQL where clause (e.g. "STATE = \'CA\' AND YEAR >= 2020"). Avoid user-supplied values; use parameterized queries if possible.'
• Enhance error messages with recovery hints. E.g., 'ArcGIS Hub returned 404. Verify org_id is correct or try a broader search query.'
• Document pagination behavior in query_layer description: 'Results capped at limit (1 - 2000, default 50). Use offset for pagination. Returns total feature count in response.'
• Add idempotency note: 'All tools are read-only and idempotent. Safe to retry on transient failures.'