Three well-named, read-only tools with clear descriptions and complete input schemas. All tools follow verb_noun naming (search_*, query_*, layer_info). Descriptions are substantive (120 - 180 chars) and explain what each tool does and when to use it. Input schemas include type definitions and parameter descriptions. However, output schemas are not documented, callers cannot predict response structure. Error handling is minimal (generic HTTP status errors). Parameters lack constraints (e.g., limit ranges are described but not enforced via enum/pattern). The layerUrl() SSRF guard is a security positive but not exposed in the tool interface.

• Document output schemas for all three tools. Example: search_datasets returns {total: number, count: number, datasets: [{id, name, summary, org, org_id, record_count, type, url}]}. query_layer and layer_info return raw ArcGIS JSON, document the expected fields (features, fields, geometryType, etc.).
• Enhance error messages with recovery guidance. E.g., 'ArcGIS Hub returned 404. Verify the org_id is correct (default: oAoeYJ1kqmAwcEC2). Try search_datasets with a broader keyword.' instead of 'ArcGIS Hub: 404'.
• Add JSON Schema constraints: search_datasets.limit as {type: 'number', minimum: 1, maximum: 50, default: 20}; query_layer.limit as {type: 'number', minimum: 1, maximum: 2000, default: 50}; query_layer.where as {type: 'string', pattern: '^[A-Za-z0-9_\s=<>!()\-\'"]+$'} to catch SQL injection attempts early.
• Implement rate limiting and quota tracking. Log tool invocations and reject calls that exceed per-minute or per-hour thresholds. Return a clear error: 'Rate limit exceeded (10 calls/min). Retry after 30 seconds.'
• Flatten and trim search_datasets response. Instead of returning raw attributes, return {datasets: [{id, name, summary, org, org_id, record_count, url}], total, count}. Strip type, snippet, description, and other metadata to reduce token overhead.