Anton exposes 24 tools with basic naming and descriptions, but lacks critical schema rigor. All tools have descriptions (10-80 chars, mostly under 100), but parameter schemas are sparse and inconsistent. Most tools accept 0-2 parameters with minimal type info. No output schemas documented. Error handling is absent, tools return raw API responses without recovery guidance. Naming is verb-noun (status, groups, pins, plan, lesson) but many are generic (status, groups, compare). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Parameter descriptions exist but lack format/constraint details (e.g., 'week' accepts 'YYYY-MM-DD Monday' but no validation guidance). No pagination documented despite tools like 'plans' and 'events' returning lists. Overall: functional but well below production baseline (194 char avg description, 100% param coverage expected for A-grade tools).

• Add output schemas to all tools. Document returned fields, types, and nesting. Example: 'Returns {status: string, groupId: string, members: [{name: string, id: string}]}'.
• Add tool annotations: mark read-only tools with readOnlyHint=true, write tools with destructiveHint=false, and idempotent tools with idempotentHint=true. This enables LLM safety reasoning.
• Enhance parameter descriptions with format constraints. Replace 'week start date (YYYY-MM-DD Monday)' with 'ISO 8601 date string, must be a Monday (e.g., 2024-01-15). Invalid dates return 400 with available weeks.'
• Add pagination to list tools: accept limit (1-100, default 20) and offset/cursor parameters. Return total count and next_cursor. Document in tool description: 'Returns up to 20 results; use offset to paginate.'
• Add error recovery guidance. For write tools, return structured errors: {code: 'INVALID_WEEK', message: 'Week must be a Monday', suggestion: 'Available weeks: 2024-01-15, 2024-01-22'}. For delete, add dry-run parameter or confirmation step.