Four tools with schemas present but significant quality gaps. Tool names lack clear action verbs (matrix:access, matrix:send, matrix:sync, matrix:rooms use colons instead of underscores, violating verb_noun convention). Descriptions exist but are generic and lack actionable context for LLM selection. Parameters have types but many lack descriptions or constraints. matrix:access has 11 parameters with minimal guidance on mutual exclusivity or dependencies. No output schemas documented. Error handling is absent from tool definitions.

• Rename tools to verb_noun convention: manage_access, send_message, sync_homeserver, list_rooms. This enables LLMs to parse intent from the name alone.
• Add enum constraints to matrix:access 'action' parameter: {"type": "string", "enum": ["list", "pair", "approve", "deny", "allow", "disallow", "group", "policy", "config"]}. Document which actions require which parameters (e.g., 'approve' requires 'code'; 'allow' requires 'mxid').
• Document output schemas for all tools. E.g., matrix:rooms with action='list' returns {"rooms": [{"roomId": string, "name": string, "memberCount": number, "joinedAt": ISO8601}], "total": number}. Include pagination (limit, offset, nextCursor).
• Add mutual exclusivity constraints to matrix:send: document that exactly one of (text, html, file, reaction) must be provided. Return clear error if multiple are passed.
• Expand tool descriptions to 100-200 chars with WHEN/WHY context. E.g., 'Send a message, file, or reaction to a Matrix room. Use this after joining a room (matrix:rooms action=join). Returns event_id for reply chains.' Include error recovery hints.