Three tools with clear verb-noun naming (search_datasets, query_layer, layer_info) and solid descriptions (150 - 200 chars). All tools have input schemas with typed properties and required fields. However, parameter descriptions lack actionable constraints (e.g., 'limit' has no min/max stated in description, only in code). Output schemas are undocumented, LLMs cannot predict response structure. Error handling is minimal (generic HTTP status errors). No enum constraints on free-form string parameters like 'where' clause. Missing guidance on chaining (e.g., 'pass url from search_datasets to query_layer'). Security: SSRF guard in layerUrl() is good, but no mention of rate limits or API quotas.

• Document output schemas for all three tools. Example: search_datasets returns {total: number | null, count: number, datasets: [{id, name, summary, org, org_id, record_count, type, url}]}. query_layer and layer_info should document their ArcGIS API response structure.
• Add min/max constraints to parameter descriptions. Change 'Max datasets (1-50, default 20)' to 'Max datasets to return (1 - 50, default 20). Values outside this range will be clamped.'
• Enhance error messages with recovery guidance. Instead of 'ArcGIS query: 401', return 'Authentication failed (401). Verify the Feature Service URL is public and accessible. Try layer_info() first to confirm the URL is valid.'
• Add tool chaining hints to search_datasets description: 'Returns Feature Service URLs. Pass each url to query_layer() to fetch data or layer_info() to inspect the schema.'
• Provide SQL syntax examples or constraints for the 'where' parameter. E.g., 'SQL where clause (e.g., "STATE = \'CA\' AND YEAR >= 2020"). See ArcGIS SQL reference for valid syntax.'