Three well-named, read-only tools with complete input schemas and solid descriptions. All tools start with action verbs (search_, query_, layer_info). Descriptions are 150 - 250 chars, within the 10 - 1024 baseline. All parameters have type definitions and descriptions. However, output schemas are NOT documented, LLMs cannot predict what fields to expect from query_layer or layer_info responses. Error handling is minimal (generic HTTP status errors with no recovery guidance). No parameter constraints (enums, ranges) despite opportunities (e.g., limit 1 - 50 for search_datasets is stated in description but not enforced in schema). Missing idempotency hints and dependency documentation.

• Add JSON Schema output documentation to each tool. Example for query_layer: 'Returns {features: [{attributes: {...}, geometry: {...}}], exceededTransferLimit: bool}'. Enables LLMs to extract fields correctly.
• Add minimum/maximum constraints to numeric parameters in inputSchema. E.g., search_datasets limit: {type: 'number', minimum: 1, maximum: 50, default: 20}. Prevents invalid values at schema-validation time.
• Enhance error messages with recovery guidance. E.g., 'ArcGIS Hub returned 404. Verify org_id is correct (default: KaARkuoKF9vrGr3P). Try search_datasets with a broader query.' Guides agent self-correction.
• Add pagination support to search_datasets. Return page_token or next_url in response so agents can fetch additional results without re-querying.
• Document tool dependencies in descriptions. E.g., query_layer: 'Requires a Feature Service url from search_datasets. Pass the url field directly.' Prevents wasted calls.