OmniWire registers 9 tools with basic descriptions and Zod schemas. However, critical gaps undermine quality: (1) Most descriptions are under 100 chars and lack WHEN/WHY context for LLM selection. (2) Parameter descriptions are minimal or absent, e.g., cybersync_search_knowledge's 'query' param has only 'Search query (matches key and value)' with no format guidance. (3) No output schemas documented, LLMs cannot predict response structure. (4) Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. (5) Naming is inconsistent: 'cybersync_*' prefix is redundant; 'omniwire_secrets' breaks the pattern. (6) No idempotency hints on write operations (sync_now, force_push, secrets set/delete). (7) Secrets tool accepts 'key' and 'value' as strings with no validation rules stated. Baseline: 90% of A+ tools have 50-200 char descriptions with explicit WHEN/WHY; 100% document output schemas; 94% have param descriptions. This server has ~40% param coverage and zero output schema docs.

• Add output schema documentation to all tools. Example: cybersync_status should document { heartbeats: [{nodeId, lastSeen, itemsCount, pendingSync}], counts: [{tool, category, count}] }.
• Expand tool descriptions to 80-150 chars with explicit WHEN/WHY. E.g., 'cybersync_sync_now: Trigger full reconciliation of all tool configs across nodes. Use when you suspect drift or after bulk config changes. Returns push/pull/conflict counts.'
• Add format and validation rules to parameter descriptions. E.g., 'query: Search query string (1-500 chars, matches key and value fields). Supports wildcards: * for any chars, ? for single char.'
• Implement error recovery guidance. Return structured errors: { error: 'node_offline', node: 'node-2', retryable: true, suggestion: 'Node is offline. Retry in 30s or exclude from sync.' }.
• Add idempotency hints and dry-run support to write tools. E.g., omniwire_secrets should accept a 'dry_run' param; cybersync_force_push should return a confirmation token before overwriting.