26 tools across 4 OJ platforms. Most tools have descriptions (194-char baseline met for many), but critical gaps exist: (1) Naming inconsistency, multiple tools named 'oj_*' across different platforms (oj_capabilities, oj_health, oj_search_problems, oj_fetch_problem repeated 4+ times) violate the pattern:tool requirement for distinct, unambiguous names. LLMs cannot distinguish which platform's oj_search_problems to call. (2) Parameter descriptions are sparse or missing entirely, many tools lack descriptions for input fields (e.g., oj_fetch_problem's 'contestId', 'taskId' lack context on format/constraints). (3) Output schemas are not visible in source, tool definitions show input schemas but no documented return types, violating pattern:tool requirement. (4) Error handling absent, no recovery guidance, retryability classification, or actionable error messages visible. (5) Composition issues, tools like oj_prepare_submission and oj_commit_submission appear tightly coupled; unclear if they're idempotent or if retry risks duplicate submissions.

• Rename tools to include platform prefix: atcoder_capabilities, codeforces_capabilities, luogu_capabilities, nowcoder_capabilities (and similarly for health, search_problems, fetch_problem). This makes tool selection unambiguous for LLMs and matches the pattern:tool naming convention (verb_noun with context).
• Document output schemas for all tools. Add a 'Returns' section to each tool description or create a separate schema registry. Specify which fields are returned, their types, and which IDs are included for chaining (e.g., contestId, taskId, problemId). This enables LLMs to plan multi-step workflows.
• Add parameter descriptions for all input fields. For each parameter, state: expected format (e.g., 'alphanumeric, 1-50 chars'), valid values (enum or pattern), and any constraints (e.g., 'must be a valid AtCoder contest ID'). Use the pattern:constrained-input approach.
• Add error handling and recovery guidance to WRITE tools (oj_commit_submission, oj_platform_run). Include: (1) error classification (retryable vs. fatal), (2) actionable recovery steps ('If submission fails due to network timeout, call oj_poll_submission with the requestId'), (3) idempotency guarantee ('Safe to retry; duplicate submissions are deduplicated by requestId').
• Consolidate oj_prepare_submission + oj_commit_submission into a single tool with a dry-run parameter, or add explicit confirmation/approval flow. Document whether oj_commit_submission is idempotent and what happens if called twice with the same intentId. This prevents accidental duplicate submissions.