Three tools with complete input schemas and descriptions. Naming follows verb_noun pattern (baltimore_recent, baltimore_layers, baltimore_query). Descriptions are detailed (150-250 chars) and explain WHEN to use each tool. However, output schemas are not documented, LLMs cannot predict return structure. Parameter descriptions are good but lack explicit constraints (e.g., limit ranges, where clause format). No error handling guidance. No tool annotations (readOnlyHint, etc.). Composition is sound: tools chain logically (layers → query). All tools are read-only, lowering risk.

• Document output schemas for all three tools. Example for baltimore_recent: 'Returns {dataset, label, service, layer, sorted_by, count, rows: [{field1, field2, ...}]}'. Specify that dates are ISO 8601 strings.
• Add explicit min/max constraints to numeric parameters. Change 'Rows to return (1-1000, default 20)' to 'Rows to return (minimum 1, maximum 1000, default 20)' and validate in code.
• Enhance error messages with recovery guidance. Instead of 'Baltimore ArcGIS: 404', return 'Service not found. Call baltimore_layers to list available services, or check the service path spelling.'
• Add readOnlyHint: true to all three tool definitions (via McpToolDefinition extension or comment). This signals to agents that these tools are safe to call without confirmation.
• Reconcile baltimore_layers description with SERVICES dict. Either add 'service_requests' and 'permits' to SERVICES, or remove them from the description.