Three well-named, read-only tools with clear descriptions and complete input schemas. All tools start with action verbs (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 required field declarations in search_datasets schema.

• Document output schemas for all three tools. For search_datasets, specify: {total: number|null, count: number, datasets: [{id, name, summary, org, org_id, record_count, type, url}]}. For query_layer and layer_info, document the ArcGIS response structure or wrap it in a consistent envelope.
• Add 'required: ["query"]' to search_datasets inputSchema to enforce the mandatory query parameter.
• Replace prose constraints with formal JSON Schema patterns or enums. E.g., url parameter: add 'pattern': '^https://[a-z0-9.-]+/(FeatureServer|MapServer)/\d+/?$' to the schema.
• Add error recovery guidance to descriptions. E.g., query_layer: 'If no results, try where="1=1" to sample all records, or refine the SQL where clause.'
• Explicitly state numeric bounds in parameter descriptions. E.g., limit: 'Max features (1 - 2000, default 50).' is good; add the same to search_datasets limit parameter.