FiberOne MCP has 22 well-named tools with consistent verb_noun patterns (get_*, create_*). All tools have descriptions (avg ~100 chars, within baseline 34-392). Input schemas are present and use Zod with type constraints (min/max for pagination). However, output schemas are NOT documented, responses are JSON-stringified without field documentation, forcing LLMs to parse unstructured text. Error handling is minimal: login/logout catch FiberOneError but most tools lack recovery guidance. Tool annotations (readOnlyHint) are correctly applied to 20 read-only tools. Parameter descriptions are adequate but lack format hints (e.g., 'email' for username param in login). No batch operations or idempotency guarantees documented.

• Document output schemas for all 18 read-only tools. Specify field names, types, and meanings (e.g., 'get_account returns {subscriber_id: string, phone: string, status: "active"|"suspended", ...}'). This enables LLMs to chain calls and extract relevant data.
• Add try-catch and error classification to all tools. Categorize errors as retryable (network timeout, rate limit) vs user-fixable (invalid category in create_outage_ticket) vs fatal (auth failure). Return actionable messages: 'Invalid category. Call get_ticket_categories() to see valid options.'
• Add format hints to parameter descriptions. Change 'username' to 'FiberOne account email (e.g., [email protected])' and 'category' to 'Ticket category from get_ticket_categories response'.
• Implement confirmation step for create_outage_ticket. Add a 'confirm' boolean parameter (default false) or split into create_outage_ticket_draft + confirm_outage_ticket to prevent accidental filing.
• Document idempotency guarantees. Specify which tools are safe to retry (all read-only tools) and which have side effects (login, logout, create_outage_ticket). Add retry guidance for transient failures.