Stroq is a security firewall/policy engine, not a production MCP server. The 6 tools are demo/test fixtures in fake-server.mjs files, not real tool implementations. Tool definitions lack proper schemas, parameter descriptions, and output documentation. Descriptions are minimal (10-30 chars). No input validation, error guidance, or structured output. This is a reference implementation for testing Stroq's rule engine, not a usable MCP server.

• Add complete JSON Schema input definitions for all 6 tools. Include type, description, required fields, and constraints (enums, min/max, patterns).
• Expand tool descriptions to 100-200 characters. Answer: What does it do? When should the LLM call it? What does it return? Example: 'Retrieve a customer record by ID or email. Returns name, account status, and contact info. Use this to verify customer identity before processing requests.'
• Document output schemas. Specify field names, types, and what downstream tools expect. E.g., read_issue should return {issue_id, title, status, assignee_id, created_at}.
• Add parameter descriptions with constraints. For 'chars' in huge: 'Number of characters to return (1 - 100000000, default 10485760 / 10 MiB). Used to test large response handling.'
• Implement error classification. Return structured errors with category (retryable|user_fixable|fatal), message, and recovery hint. E.g., 'Customer not found. Try search_customers() with a partial name.'