Two tools with clear, detailed descriptions and well-structured input schemas. property_lookup has comprehensive parameter documentation with helpful guidance (e.g., DC quadrant recommendation). property_coverage is simpler but correctly specified. Both tools are READ_ONLY and stateless, aligning with the server's design philosophy. Naming is clear and verb-based. However, output schemas are not explicitly documented in the source code, only inferred from descriptions. Error handling guidance is implicit (shaped empty results for out-of-coverage) but not formalized in tool definitions. No tool annotations (readOnlyHint, etc.) present.

• Add formal JSON Schema output documentation for both tools. For property_lookup, document the structure of the response object, including fields like covered (boolean), source_name (string), source_url (string), sales_history (object), owner (object), assessment (object), characteristics (object), fields_available (array), note (string), and other_matches (array). For property_coverage, document the array of jurisdiction objects with slug, name, source_name, source_url, field availability flags, vintage, cadence, and caveats.
• Add tool annotations to the tool definitions: readOnlyHint: true for both tools (they do not modify state). This signals to agents that these tools are safe to call speculatively and can be retried without side effects.
• Formalize error handling by documenting expected error cases in tool descriptions. E.g., 'Returns {covered: false, jurisdiction: "<inferred>", supported_jurisdictions: [...]} for addresses outside coverage. No error thrown; shaped response indicates out-of-coverage.' Add a note: 'This tool never fabricates records; empty coverage is explicit.'
• Add format and constraint documentation to the address parameter. E.g., 'Street address (required, 5 - 200 characters). Can include city, state, ZIP. For DC, include quadrant (NW/NE/SW/SE) to avoid ambiguity, omitting it may match up to four properties, all returned in other_matches.'
• Consider adding optional limit and offset parameters to property_lookup to cap the number of matches returned (e.g., limit: 1 - 50, default 10) and enable pagination for ambiguous addresses. Document in property_coverage whether result count is bounded.