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 concise (100 - 200 chars) and explain WHAT, WHEN, and WHAT-TO-DO-NEXT. Input schemas include types and descriptions for all parameters. However, output schemas are NOT documented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., 'url must be https and end in /FeatureServer/<n>' is stated in code but not in schema descriptions). No error handling guidance in descriptions. Missing pagination details for search_datasets despite returning a 'total' field.

• Add output schema documentation to each tool. Example for search_datasets: 'Returns {total: number, count: number, datasets: [{id, name, summary, org, org_id, record_count, type, url}]}'. This enables LLMs to plan downstream calls and extract the right fields.
• Enhance parameter descriptions with format constraints. For 'url': 'Feature/Map Service layer url (https only, must end in /FeatureServer/<n> or /MapServer/<n>, no IP addresses or localhost).'
• Add error recovery guidance to tool descriptions. Example: 'If query fails with 404, the layer url may be invalid, call layer_info first to verify the url and schema.'
• Document pagination for search_datasets. Add to description: 'Results are paginated by limit (1-50, default 20). To fetch all datasets, iterate by incrementing offset or use limit=50 and check if count < limit.'
• Warn about SQL injection in query_layer description: 'The where clause accepts SQL, escape user input to prevent injection. Use parameterized queries or validate input against expected field names and types.'