Server has 6 tools with complete schemas and descriptions. Naming is action-oriented (respond, extract, vision, token_count, available, compress). Descriptions are adequate (100-200 chars, within baseline). However, parameter descriptions are sparse or missing in several tools (vision lacks image_path format guidance; compress lacks target_tokens range). Output schemas are not documented. Error handling is basic (returns ok/text tuples with error messages, but no recovery guidance or categorization). No tool annotations (readOnlyHint, destructiveHint). Missing idempotency guarantees and per-item failure reporting for batch-like operations.

• Document output schema for each tool. E.g., respond returns {type: 'string', description: 'Generated text response'}; extract returns {type: 'object', properties: {<field_name>: <field_type>}}; available returns {type: 'object', properties: {system_model: string, pcc_model: string}}.
• Add format and range constraints to parameter descriptions. vision: 'Absolute path to image file (JPEG, PNG, WebP; max 5MB)'. compress: 'target_tokens: integer, 100 - 10000 (default 500)'.
• Add tool annotations to schema. All tools should include 'readOnlyHint: true' in their schema metadata since they do not modify state.
• Enhance error messages with recovery guidance. E.g., 'extract: schema build failed (fm CLI error). Verify text is valid UTF-8 and fields list is non-empty. Retry with simpler field types (string, int).'
• Document idempotency and timeout behavior. E.g., 'compress: deterministic output for same input; timeout 600s; retryable on timeout; not retryable on file-not-found or permission-denied.'