RenterShield defines 2 tools with clear action verbs and reasonable descriptions (194 - 250 chars, within baseline 34 - 392). Both tools have input schemas with Zod validation. However, parameter descriptions are missing entirely, the schema shows type but no explanation of what each parameter controls or its constraints. Output schemas are documented in TypeScript types but not exposed to MCP clients. Error handling is present but generic ('Unauthorized', 'Rate limit: {reason}'). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite both being read-only operations.

• Add parameter descriptions to analyze_lease schema: 'text' → 'The residential lease document text to analyze (min 100, max 50000 characters)', 'jurisdiction' → 'The jurisdiction code (one of: ontario, bc, nyc, texas, general)', 'unitType' → 'Optional unit type classification (e.g., rent-stabilized, market-rate), affects applicable rules'.
• Convert 'jurisdiction' to an enum constraint in Zod: z.enum(['ontario', 'bc', 'nyc', 'texas', 'general']) instead of z.string(). This prevents hallucinated values and self-documents valid options.
• Document output schema in the tool definition. Add a 'returns' field or comment describing RedFlag[] structure: 'Returns array of {clause, severity, issue, citation, recommendation} objects plus summary and disclaimer.'
• Add readOnlyHint: true to both tool definitions to signal they are safe to call without user confirmation.
• Enhance error messages with recovery guidance: 'Rate limit exceeded. Wait 60 seconds before retrying, or contact [email protected].' For 'Unauthorized': 'Missing or invalid MCP token. Ensure your client includes a valid Bearer token in the Authorization header.'