Two tools with complete input schemas and descriptions. Tool names follow verb_noun pattern (hansard_search, hansard_contributions_search). Descriptions are present and adequate (100-150 chars), exceeding the 10-char minimum but below the 194-char production baseline. Parameters are well-typed with Zod schemas and descriptions. However, output schemas are not documented, responses are JSON stringified without field-level documentation. Error handling returns raw error messages without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations. Parameter descriptions lack format constraints (e.g., date format yyyy-mm-dd is mentioned but not enforced in schema).

• Document output schemas for both tools. Specify the structure of the 'result' object returned by hansardService.search() and hansardService.searchContributions(), including field names, types, and what each field represents.
• Enhance error handling with recovery guidance. Catch specific error types (network, not-found, validation) and return structured errors: {error: 'not_found', message: '...', suggestion: 'Try broadening your search term or adjusting date filters.'}
• Add tool annotations. Register both tools with readOnlyHint: true since they only query data and do not modify state.
• Enforce date format constraints. Use Zod's .regex() or .datetime() to validate startDate and endDate as yyyy-mm-dd format, rejecting invalid dates at parse time.
• Document and enforce result limits. Add explicit limit enforcement in hansardService.search() and hansardService.searchContributions(); return pagination metadata (total, hasMore, nextCursor) to guide multi-page queries.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry