StrataFS exposes 4 tools with basic schemas and descriptions, but falls short of production quality. The search tool has a comprehensive parameter set (16 params) with types and descriptions, but lacks output schema documentation. The documents, health, and queue/stats tools have minimal descriptions (under 50 chars) and no visible output schemas. No error handling guidance, no parameter validation rules, and no tool annotations. Descriptions are generic and do not explain WHEN to use each tool or what the LLM should expect in responses. Parameter descriptions exist but are terse. No evidence of idempotency markers, permission gates, or recovery guidance.

• Document output schemas for all tools. For search, specify: {results: [{id, path, score, content?, metadata?}], total_count, next_offset?}. For documents, specify: {file_id, file_path, content, chunks?, metadata?}.
• Expand health and queue/stats descriptions to 100-150 chars explaining purpose and when to call. E.g., 'Returns server health status and version. Call before executing searches to verify service availability.'
• Add parameter constraints: search limit (1-1000, default 20), offset (≥0), min_size/max_size (bytes, ≥0), weight_* (0.0-1.0). Document in descriptions.
• Add error handling guidance: 'If search returns 0 results, try broadening the query or removing filters. If documents returns 404, verify file_id or file_path exists.'
• Add tool annotations: mark all four tools with readOnlyHint=true to signal they are safe to call without user confirmation.