Single tool 'cross_layer_query' has a reasonable description (127 chars, within 10-1024 range) and declares input schema with three properties. However, the schema lacks critical details: parameter descriptions are minimal ('Array of layer slugs to query' is the only substantive one), 'geometry' and 'filters' objects have no type constraints or field documentation, and no output schema is documented. The tool name does not follow verb_noun convention (should be 'query_layers' or 'search_geographic_layers'). No error handling guidance, no pagination support despite returning potentially large geographic datasets, and no indication of result limits. The schema is present but incomplete, parameters lack proper type definitions and descriptions.

• Rename tool to 'query_geographic_layers' or 'search_layers' to follow verb_noun convention and clarify intent.
• Document 'geometry' parameter with GeoJSON schema reference and example: 'GeoJSON geometry object (Point, Polygon, etc.) for spatial filtering. Example: {"type": "Point", "coordinates": [13.4, 52.5]}'.
• Document 'filters' parameter with allowed field names and types: 'Object with property-based filters. Allowed fields: {name: string, population_min: number, population_max: number, ...}'.
• Add output schema documentation: 'Returns array of feature objects with fields: {id, layer_slug, name, geometry, properties, aggregated_values}. Limited to 50 results; use offset/limit for pagination.'
• Add 'limit' (default 20, max 100) and 'offset' parameters to support pagination and prevent context window exhaustion.