Two tools with minimal definitions. accela_auth_status has empty input schema ({}), which is acceptable for a read-only status check, but both tools lack substantive descriptions (under 100 chars). accela_login has a proper 2-parameter schema with type strings and descriptions, but the tool description itself is generic and doesn't explain prerequisites, return values, or error recovery paths. No output schemas documented. No error handling guidance. No parameter constraints (e.g., enum for environment). Naming is clear (verb_noun pattern), but descriptions fall short of the 50-200 char LLM-optimized baseline. No tool annotations (readOnlyHint, destructiveHint). This is a bootstrap-only server with minimal surface area, but even minimal tools need complete, actionable descriptions.

• Expand accela_auth_status description to ~100 chars: 'Check if the current Accela OAuth token is valid and not expired. Returns token expiry time, agency, and environment. Call this before attempting API operations to detect stale credentials.'
• Expand accela_login description to ~150 chars: 'Authenticate with Accela using OAuth 2.0 Authorization Code flow. Saves tokens to disk for future API calls. Required before any other Accela tools can be used. Returns access token, refresh token, and expiry times.'
• Add enum constraint to accela_login 'environment' parameter: {"type": "string", "enum": ["PROD", "TEST"], "description": "Accela environment: PROD for production, TEST for sandbox."}
• Document output schema for accela_login: returns {"access_token": string, "refresh_token": string, "expires_in": integer, "agency": string, "environment": string}. Include in description or as separate schema field.
• Add error handling guidance to accela_login: 'If authentication fails, verify agency name and environment are correct. If token refresh fails, re-run accela_login to obtain fresh credentials.'

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

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