Two tools with minimal schema documentation and weak descriptions. 'ask' and 'report_message' have basic input schemas (question/message strings, timeout integer) but lack output schema documentation. Descriptions are present but generic (10-50 chars), below the 50-200 char LLM-optimized baseline. No parameter constraints (enums, ranges), no error handling guidance, no idempotency hints. Tool names lack clarity on state mutation (ask/report_message don't signal they interact with Discord). No tool annotations (readOnlyHint, destructiveHint). Schema completeness is low, output types are undocumented.

• Document output schemas explicitly. E.g., 'ask returns {response: string, timestamp: ISO8601, user_id: string}' and 'report_message returns {success: boolean, message_id: string, sent_at: ISO8601}'.
• Expand descriptions to 100-150 chars with WHEN/WHY context. E.g., 'ask: Pose a question to the human via Discord and wait for their response (up to timeout seconds). Use when you need user input or confirmation. Returns the user's text response or timeout error.'
• Add parameter constraints: timeout as integer with min=1, max=300 (seconds); question as string with minLength=1, maxLength=2000. Document in descriptions: 'timeout: Wait duration in seconds (1-300, default 3)'.
• Add error handling guidance in descriptions. E.g., 'If user does not respond within timeout, returns error code TIMEOUT. If Discord is unreachable, returns error code DISCORD_UNAVAILABLE, consider retrying or falling back to report_message.'
• Rename tools for clarity: 'ask' → 'request_user_input_discord' or 'ask_human_discord'; 'report_message' → 'send_message_discord' or 'notify_human_discord'. Include Discord context in the name.

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

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