Server has 3 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (world-id.verify, echo, advanced-operation). Schemas use Zod validation with proper types. However, descriptions are minimal (34-72 chars, below the 50-200 char baseline for LLM optimization). Parameter descriptions exist but lack actionable guidance on constraints, dependencies, and error recovery. Output schemas are not documented. Error handling returns generic messages without recovery guidance. Security model relies on JWT tokens passed as parameters, which is acceptable but not ideal for sensitive operations.

• Expand tool descriptions to 100-200 chars. Example: 'Verify a World ID proof and establish an authenticated session. Returns a JWT token valid for 1 hour. Required before calling echo or advanced-operation. Supports orb, secure_document, document, and device verification levels.'
• Document output schemas explicitly. Add a 'Returns' section to each tool: world-id.verify returns {token: string, scopes: string[], expiresAt: ISO8601}; echo returns {message: string}; advanced-operation returns {result: string, status: 'success'|'failed'}.
• Add constraint descriptions to parameters. Example: 'token (string, JWT from world-id.verify, expires in 1 hour, required scopes: [operation_name])' instead of just 'JWT from world-id.verify'.
• Enhance error messages with recovery guidance. Instead of 'verificationLevel too low: need at least orb', return 'Verification level too low. Your proof is [current_level]; this operation requires [required_level]. Re-verify with a higher verification method (e.g., orb instead of device).'
• Rename 'advanced-operation' to a specific action verb. If it executes a privileged operation, name it 'execute_privileged_operation' or 'perform_orb_verified_action' so LLMs infer intent from the name alone.

Inferred effective spec: 2025-06-18+.

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