This server has significant definition quality gaps. Tool descriptions are present but often vague and written in French without English translations, limiting LLM comprehension. Most critically, parameter descriptions lack actionable detail, many omit type constraints, valid ranges, or format specifications. Input schemas exist but are minimal (mostly just property names and basic types). No output schemas are documented. Error handling is absent from tool definitions. The 'listen' tool accepts a timeout parameter with constraints (10-60 min) mentioned only in broker code, not in the schema. No tool has annotations (readOnlyHint, destructiveHint, idempotentHint). Naming is generally acceptable (verb_noun pattern), but descriptions average ~60 chars, below the 194-char baseline for A+ tools.

• Expand all tool descriptions to 100-200 characters in English. Include WHAT the tool does, WHEN to use it (vs similar tools), and WHAT it returns. Example: 'talk' → 'Send a message to a conversation or direct message to a friend. Use for group chats (provide conversationId) or DMs (provide friendKey). Returns messageId and notification count.'
• Add min/max constraints to numeric parameters in schemas. For 'listen', add 'minimum: 10, maximum: 60' to the timeout property. For 'history', add 'minimum: 1, maximum: 100' to the limit property.
• Document parameter dependencies and mutual exclusivity. For 'talk', clarify: 'Either conversationId OR (to + friendKey) required. Use conversationId for group chats; use to + friendKey for direct messages.'
• Add output schema documentation to each tool. Example for 'history': 'Returns array of message objects with fields: id (string), sender_id (string), content (string), timestamp (ISO 8601), conversation_id (string).'
• Add tool annotations to write operations. Mark 'talk', 'register', 'create_conversation', 'leave_conversation', 'set_status', 'add_friend', 'remove_friend', 'notifications' with destructiveHint: true or idempotentHint: true as appropriate.